Oracle® Application Server Upgrade and Compatibility Guide 10g (10.1.4.0.1) for Microsoft Windows Part Number B28235-01 |
|
|
View PDF |
This section includes a description of the error messages that might be generated during the upgrade of the OracleAS Metadata Repository. Refer to the following sections for more information:
Section E.1, "Error Messages Generated By the Metadata Repository Upgrade Assistant"
Section E.2, "UDDI Registry OracleAS Metadata Repository Upgrade Error Messages"
This section describes the error messages generated by the Metadata Repository Upgrade Assistant.
cn=orcladmin
) account, you entered an incorrect password.cn=orcladmin
password.The value of the -oid_host
argument and -oid_ssl_port
arguments must match the value of the corresponding properties defined in following configuration file in the Identity Management Oracle home:
IDENTITY_MANAGEMENT_HOME\config\ias.properties
For example:
OIDhost=sys42.acme.com OIDsslport=636
Specifically, be sure you are logged in to the computer where the OracleAS Metadata Repository is running as the same user who installed the Release 2 (9.0.2) or 10g (9.0.4) OracleAS Metadata Repository.
If you are logged in as the appropriate user, note the name of the problem file and contact Oracle support.
For more information, see Section D.2, "Reviewing the MRUA Log Files".
If you are running from the OracleAS Metadata Repository Upgrade Assistant and Utilities CD–ROM, be sure the CD is mounted properly.
Contact Oracle Support.
If you are running from the OracleAS Metadata Repository Upgrade Assistant and Utilities CD–ROM, be sure the CD is mounted properly.
Contact Oracle Support.
If you are running from the OracleAS Metadata Repository Upgrade Assistant and Utilities CD–ROM, be sure the CD is mounted properly.
Contact Oracle Support.
For more information, see Section D.2, "Reviewing the MRUA Log Files".
For more information, see Section D.2, "Reviewing the MRUA Log Files".
For more information, see Section D.2, "Reviewing the MRUA Log Files".
For more information, see Section D.2, "Reviewing the MRUA Log Files".
This section contains error messages that are specific to the OracleAS Portal Repository upgrade. Error messages that are generated after the upgrade has progressed past the precheck stage indicate that the OracleAS Portal schema has had modifications. If you receive any error messages after the precheck step, you must fix the problem, restore your database from its backup, and then run the upgrade again. This section contains the following subsections:
If the following lines are found in the log, then the error may be because Oracle Text is not installed correctly.
### PHASE I STEP 8: Perform pre upgrade checks Upgrade step started at Fri Apr 4 02:28:18 2003 Running upg/common/utlchvpd.sql Connected Calling DoPreChecks() Starting precheck at Fri Apr 4 02:28:21 2003 Calling upg/common/sysuppre.sql Connected.
ERROR: An unexpected exception was raised during the upgrade prechecks:
ORA-00942: table or view does not exist ----- PL/SQL Call Stack ----- object handle line number object name 80bc68c4 76 anonymous block 80bc68c4 380 anonymous block
Verify if the Oracle Text component is installed and reinstall it if it does not exist. Refer to the Oracle Application Server Portal Configuration Guide.
sysdba
by creating a orapw<SID>
file in the database Oracle Home's dbs
directory by running orapwd with the same password used by the SYS database account.uptxtdrp
script in the upgrade log to see what should be done. The entire uptxtdrp.log
is appended to the error message output in the upgrade log.If the error was encountered while removing the synchronization or optimization jobs, make sure that these jobs are removed from the job queue before restarting the upgrade. For information about breaking or removing jobs, refer to the Managing Job Queues chapter of the Oracle9i Database Administrator's Guide.
After upgrading, manually recreate the Oracle Text indexes and the synchronization and optimization jobs if you wish to use Oracle Text searching in your OracleAS Portal. Refer to the Oracle Application Server Portal Configuration Guide for complete instructions.
ERROR: granting execute on SCHEMA1.CHECK_SAL to SCHEMA1B as SCHEMA1--ORA-01001:invalid cursor
In this case, there is a form in a database provider based on SCHEMA1B
, on the procedure SCHEMA1.CHECK_SAL
and either the procedure CHECK_SAL
is missing or one of the schemas SCHEMA1
or SCHEMA1B
is missing. Therefore, the form will not run. However, it would not have run before the upgrade either.
orapw<SID>
file in the database Oracle Home's dbs directory by running orapwd
with the same password used by the SYS database account.Loading Java Classes - soap.jar
errors : class oracle/soap/providers/ejbprov/<class> ORA-29521: referenced name javax/ejb/<name> could not be found The following operations failed class oracle/soap/providers/ejbprov/<provider>: resolution exiting : Failures occurred during processing
http://metalink.oracle.com
. Run the upgrade again after the steps have been completed.revoke exempt access policy from <portal_schema_user>;
Also verify the Oracle9iAS Portal schema user does not inherit the EXEMPT ACCESS POLICY privilege from any of its assigned roles.
An example of a post-upgrade task is checking whether VPD is enabled correctly. Another example of a post-upgrade task is verifying if the SSO Partner Configuration has been run.
upgrade.csh
) terminated abnormally (for example, with Ctrl+C
), the lock file created during upgrade (upgcsh.lok
) is not deleted. Therefore, if you attempt to start another upgrade, you will see this message. In this case you will need to manually delete the lock file. You should delete this lock file only when an upgrade has abnormally terminated, not if an upgrade is actually running. You can find the lock file in the location from where you ran the upgrade script.CTXSYS
) beginning with DRI
or CTX_
are invalid.OracleAS Portal has not been configured correctly for the Oracle Internet Directory.
Oracle Internet Directory server is not running.
An unexpected error was encountered.
Note: Only certain fatal errors are detected in this check. It is possible for the version to be updated even if other fatal errors are encountered. |
WARNING: 1 session cleanup job(s) detected in the SYS schema.
MY_TABLE
. Then MY_TABLE
is dropped. For example:
WARNING: Component SCOTT.MY_QBE has errors. Please check that all the objects it is based on are present.
The table on which the calendar is based is missing.
The schema on which the database provider containing the calendar is based on is missing.
Examples:
WARNING: Could not Parse select a1.HIREDATE the_date, a1.ENAME the_name, null the_name_link, null the_date_link, null the_target from test_1.EMP_1 a1 order by a1.HIREDATE as TEST_1. WARNING: Could not Parse select b2.HIREDATE the_date, b2.ENAME the_name, null the_name_link, null the_date_link, null the_target from test_2.EMP_2 b2 order by b2.HIREDATE as TEST_2.
This warning usually occurs while upgrading a Oracle9iAS Portal which was created using Oracle export/import. Not all of the schemas on which the Portlet Builder components are based were imported. Calendars which show this warning cannot be used unless the missing objects are supplied, and the calendar component is regenerated.
Log on to your OracleAS Portal.
Click the Administer tab.
In the Services portlet, click the Global Settings link.
Click the Configuration tab.
Locate the Default JPDK Instance URL field. Usually this value is <portal_middle_tier_protocol>://<portal_middle_tier_host>:<portal_middle_tier_port>/jpdk/servlet/soaprouter/
. If there is no value in this field, you will receive the warning mentioned above in your upgrade log.
ORACLE_HOME\portal\upg\plsql\upg\9025-9026\wws\updmturl.sql
The script updates the middle-tier URL for the PORTLETBLDGTOOLS, OMNIPORTLET, and WEBCLIPPING providers in the providers table. This script is not run from the upgrade script. Run it in standalone mode to update the URLs. For example:
@updmturl.sql http my.domain.com 80
where:
http
is the middle-tier's protocol
my.domain.com
is the middle-tier's host
80
is the middle-tier's port
http://portalcenter.oracle.com
.WARNING: Only 38 % of components in wwv_modules$ table are production components.
WARNING: Removed session cleanup job: 63 from the SYS schema.
sqlplus
in a Oracle9iAS Portal schema to check whether the session cleanup job exists:
ORACLE_HOME\portal\upg\plsql\wwc\ctxjget.sql
If this job is missing in any Oracle9iAS Portal schema then you can create it by running the script ctxjsub.sql
from sqlplus
in that schema, located in the same directory.
WWPRO_OFFLINE_PRO_PORTLET$
WWPRO_OFFLINE_PRO_PORTLET_NLS$
WWPRO_PORTLET_METADATA_USER$
In all other cases, there may have been a problem with a previous installation or upgrade procedure. Contact Oracle Support for more information.
job_queue_processes
to 0, or by restricting logins.job_queue_processes
is set to one or greater, and that logins are not restricted by changing the system disable restricted session.<upgrade_tmp_dir>/nonportal.log
and fix the compilation problems associated with your objects. Compilation errors in your packages may cause your portlets to render incorrectly.WARNING User/Role SCOTTB does not exist. Application based on SCOTTB will have errors.
In this case, the database provider would not have been accessible before the upgrade either.