Oracle® Collaboration Suite Upgrade Guide 10g Release 1 (10.1.1) for hp-ux PA-RISC (64-bit), Linux x86 and Solaris Operating Environment (SPARC) Part Number B14490-03 |
|
|
View PDF |
This appendix provides information about the error messages you may encounter when upgrading your Oracle Collaboration Suite installations or when running multiple versions Oracle Collaboration Suite.
The following sections provide information about error messages that may appear in the OracleAS Upgrade Assistant, Oracle Application Server Metadata Repository Upgrade Assistant, or Oracle Universal Installer log files when you are upgrading your Oracle Collaboration Suite instances to 10g Release 1 (10.1.1):
Error Messages When Upgrading Instance Configuration Components
Error Messages When Upgrading Oracle Application Server Web Services UDDI Registry
Error Messages When Upgrading Oracle Application Server Portal
This section contains upgrade error messages that are common to all Oracle Application Server 10g (9.0.4) components.
This section contains error messages that are specific to the upgrade of your Oracle Application Server 10g (9.0.4) instance configuration.
This section contains error messages that are specific to Oracle HTTP Server.
This followins sections contains error messages that are specific to the Oracle Application Server UDDI Registry:
This section describes the error messages, their causes, and suggested actions that are specific to the mod_plsql upgrade in the 10.1.2 Middle-tier upgrade.
This section describes the error and warning messages, their causes, and suggested actions that you may encounter when upgrading OracleAS Portal. The messages have been listed in numeric or alphabetical order in each subsection for easy location. For more information, refer to the Upgrade documentation, available on OracleAS Portal Center at http://portalcenter.oracle.com/upgrades
. This section contains the following subsections:
The following public error messages are specific to the OracleAS Portal upgrade in the 10.1.2 Middle-tier upgrade.
emtab
file on Solaris and Linux platforms, or from the registry on Windows platforms.For Solaris, /var/opt/oracle/emtab
file.
For Linux, /etc/emtab
file.
For Windows, check the em_loc
subkey under the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
key in the registry.
targets.xml
file.targets.xml
exists in the Oracle home running the Oracle Enterprise Manager Services. In release 9.0.4, the Oracle Enterprise Manager Oracle home will be the same as the source Oracle home. In release 9.0.2, the active Oracle Enterprise Manager home location is specified in the emtab
file on UNIX and in the em_loc
subkey in the registry on Windows under the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
key.emtab
file, which is used to determine which Oracle home is running the Oracle Enterprise Manager services, is not found./var/opt/oracle
on Solaris and /etc
on Linux) and that the "DEFAULT" property refers to the correct Oracle home.em_loc
subkey exists under the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
key in the registry.SOURCE_ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/omniPortlet/WEB-INF/providers/omniPortlet/
provider.xml
, or the file contained an invalid encodeHtmlField Setting.<encodeHtmlField>
tag in the following configuration file from the source installation to the target installation:
SOURCE_ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/omniPortlet/WEB-INF/providers/omniPortlet/provider.xml
provider.xml
, or the file contained an invalid exportConnectionInfo Setting.<exportConnectionInfo>
tag in following configuration file from the source installation to the target installation:
SOURCE_ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/omniPortlet/WEB-INF/providers/omniPortlet/provider.xml
provider.xml
, or the file contained an invalid Local Personalization Level.<localePersonalizationLevel>
tag in the following configuration file from the source installation to the target installation:
SOURCE_ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/omniPortlet/WEB-INF/providers/omniPortlet/provider.xml
provider.xml
, or the file contained invalid Preference Store Settings.<preferenceStore>
tag in the following configuration file from the source installation to the target installation:
SOURCE_ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/omniPortlet/WEB-INF/providers/omniPortlet/provider.xml
provider.xml
, or the file contained invalid Proxy Settings.<proxyInfo>
tag in following source file from the source installation to the target installation:
SOURCE_ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/omniPortlet/WEB-INF/providers/omniPortlet/provider.xml
provider.xml
, or the file contained invalid Security Repository Settings.<vaultId>
tag in following configuration file from the source installation to the target installation:
SOURCE_ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/omniPortlet/WEB-INF/providers/omniPortlet/provider.xml
provider.xml
, or the file contained an invalid Trusted Certificate Location.<trustedCertificateLocation>
tag in the following configuration file from the source installation to the target installation:
SOURCE_ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/omniPortlet/WEB-INF/providers/omniPortlet/provider.xml
targets.xml
file.oracle_ias
) and Oracle HTTP server (target type oracle_apache
) exist in the following configuration file, and verify that valid entries exist for the various properties of these targets:
DESTINATION_ORACLE_HOME/sysman/emd/targets.xml
targets.xml
file.oracle_ias
) and Oracle HTTP server (target type oracle_apache
) exist in the following configuration file, and verify that valid entries exist for the various properties of these targets:
SOURCE_ORACLE_HOME/sysman/emd/targets.xml
For example, if the source directory is:
SOURCE_ORACLE_HOME/j2ee/OC4J_Portal/applications/jpdk/jpdk/WEB-INF/PORTLETBLDGTOOLS/provider/myprovider.
Then the corresponding target directory is:
DESTINATION_ORACLE_HOME/j2ee/OC4J_Portal/applications/jpdk/jpdk/WEB-INF/PORTLETBLDGTOOLS/provider/myprovider.
Note:
Special care should be taken if the directory to be copied contains the fileprovider.xml
. The source file can contain multiple <preferenceStore>
entries. If this is the case, perform one of the following two steps, depending on whether a <prefStoreName>
tag is defined in the source provider.xml
file:
If it is defined, select, the tag whose name attribute value matches the <prefStoreName>
tag out of all the <preferenceStore>
tags in that file and migrate that <preferenceStore>
tag to the destination provider.xml
file. If it is not defined, copy the first <preferenceStore>
tag of all the <preferenceStore>
tags from the source provider.xml
file, to the destination provider.xml
file.
If there is only one occurrence of the <preferenceStore>
tag in the source provider.xml
file, copy this tag to the destination provider.xml
file.
<env-entry-mapping>
tags from the orion-web.xml file in the source Oracle home to the orion-web.xml file in the destination Oracle home.
The orion-web.xml file is located in the following directory of the source Oracle home and the destination Oracle home:
SOURCE_ORACLE_HOME\j2ee\OC4J_Portal\application-deployments\jpdk\source\orion-web.xml
DESTINATION_ORACLE_HOME\j2ee\OC4J_Portal\application-deployments\jpdk\source\orion-web.xml file
<env-entry-mapping>
tags from the source to the destination orion-web.xml
file.<providerGroup>
tags to the target iasProviders.xml
file failed during jpdk upgrade.<providerGroup>
tags under the <providerGroups>
tag from the source iasProviders.xml
file to the destination. Copy only the <providerGroup>
tag if it does not start with 'oracle', Paste it under the root <providerGroups>
tag. The source and the target file will be at the following locations:
SOURCE_ORACLE_HOME/portal/pdkjava/providerGroups/iasProviders.xml
DESTINATION_ORACLE_HOME/portal/pdkjava/providerGroups/iasProviders.xml
<preferenceStore>
tag from the source to the destination provider.xml
file during jpdk upgrade. The exact location of the provider.xml
file is provided in the error message.<preferenceStore>
entries. If this is the case, perform one of the following two steps, depending on whether a <prefStoreName>
tag is defined in the source provider.xml
file:
If it is defined, select, the tag whose name attribute value matches the <prefStoreName>
tag out of all the <preferenceStore>
tags in that file and migrate that <preferenceStore>
tag to the destination provider.xml
file.
If it is not defined, copy the first <preferenceStore>
tag of all the <preferenceStore>
tags from the source provider.xml
file, to the destination provider.xml
file.
If there is only one occurrence of the <preferenceStore>
tag in the source provider.xml
file, copy this tag to the destination provider.xml
file.
<providerGroup>
tag from the source to the destination <provider_registry>
file during jpdk upgrade. The <provider_registry>
file could be progrp.xml
or provideruiacls.xml
.propgrp.xml
file can be located in the following places:
SOURCE_ORACLE_HOME
/j2ee/OC4J_Portal/applications/jpdk/jpdk/WEB-INF/deployment_providerui/progrp.xml
.
SOURCE_ORACLE_HOME
/j2ee/OC4J_Portal/applications/portalTools/providerBuilder/WEB-INF/deployment_providerui/progrp.xml
.
The provideruiacls.xml
file can be located in one of the following places:
SOURCE_ORACLE_HOME
/j2ee/OC4J_Portal/applications/jpdk/jpdk/WEB-INF/deployment_providerui/provideruiacls.xml
or
SOURCE_ORACLE_HOME
/j2ee/OC4J_Portal/applications/portalTools/providerBuilder/WEB-INF/deployment_providerui/provideruiacls.xml
.
Manually copy the <providerGroup>
tag, located under the <providerGroups>
tag to the destination propgrp.xml
file.
Note:
If you are upgrading from version 9.0.2, you will see that all the<providerGroups>
tags are located under the <webNode>
tag, instead of under the <providerGroups>
tags (version 9.0.4 and up) In this case, select all the <providerGroup>
tags located under the <webNode>
tag from the source and migrate them to the <providerGroups>
node tag in the destination propgrp.xml
file.For provideruiacls.xml
file, manually copy the file from the source to the destination location and add the following entry to the corresponding target file:
<user name="portal" privilege="500"/>
under the <object name="ANY_PROVIDER" owner="providerui">
tag, if this tag is present.
and under the <object name="ANY_PORTLET" owner="providerui">
tag, if this tag is present.
provider.xml
, or the file contained invalid Proxy Settings.<proxyInfo>
tag in the following configuration file from the source installation to the target installation:
SOURCE_ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/webClipping/WEB-INF/providers/webClipping/provider.xml
provider.xml
, or the file contained invalid Security Repository Settings.<repositoryInfo>
tag in the following configuration file from the source installation to the target installation:
SOURCE_ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/webClipping/WEB-INF/providers/webClipping/provider.xml
provider.xml
, or the file contained an invalid Trusted Certificate Location Setting.<trustedCertificateLocation>
tag in the following configuration file from the source installation to the target installation.
SOURCE_ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/webClipping/WEB-INF/providers/webClipping/provider.xml
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.
This section contains error messages that are specific to the Oracle Ultra Search.
This section contains error messages that are specific to the OracleAS Wireless.
DESTINATION_ORACLE_HOME/wireless/server/classes
[TIMESTAMP] NOTIFICATION:1 Wireless: LocalCfgSession: Failed to send LocalCfgChangeEvnet due to the following DB Access Error: [TIMESTAMP] NOTIFICATION:1 Wireless: LocalCfgSession: SQLCODE is -20001 [TIMESTAMP] NOTIFICATION:1 Wireless: LocalCfgSession: SQLERROR is NO INSTANCE UNDER [MID-OH] ON [MACHINE] HAS BEEN STARTED