99 UPGCMP-00019 to UPGCMP-06005

UPGCMP-00019: Component {0} is not in the SCHEMA_VERSION_REGISTRY for namespace {1}.

Cause: Repository upgrade framework detected that the named component was missing a required entry in SCHEMA_VERSION_REGISTRY. This might be due to an internal error or incorrect configuration before the upgrade was performed. The component might be missing from the repository database.

Action: Verify that the component already has been created in the repository database by the Repository Creation Utility under the same namespace being used for upgrade. Retry the upgrade. If the Repository Creation Utility has created the component schemas and the error persists, contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00037: Component {0} is not present in the SCHEMA_VERSION_REGISTRY for namespace {1}.

Cause: The repository upgrade component-specific software module discovered that an optional component was not present in SCHEMA_VERSION_REGISTRY. This is an informational message.

Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00038: Component {0} app_registry entry is: {1} {2}.

Cause: Repository upgrade component-specific software module detected that the component had an entry in the 10g APP_REGISTRY view. This is an informational message.

Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00039: Component {0} schema_registry entry is: {1} {2} in the namespace {3}.

Cause: Repository upgrade component-specific software module logged this data that was retrieved from SCHEMA_VERSION_REGISTRY. This is an informational message.

Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00045: failure reading from app_registry

Cause: Repository upgrade component-specific software module encountered an error while attempting to access the OracleAS 10g APP_REGISTRY view. This is an internal error.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00046: Component {0} is not present in app_registry.

Cause: Repository upgrade component-specific software module detected that a component was missing an entry in the OracleAS 10g APP_REGISTRY view. This error condition will cause the examination phase of upgrade to fail.

Action: Verify that the database being upgraded contains an OracleAS metadata repository. If the problem persists notify Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00047: Component {0} is not present in app_registry.

Cause: Repository upgrade component-specific software module detected that an optional component was missing from the 10g APP_REGISTRY view. This is an informational message.

Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00048: SQL version and status query failed for component {0}.

Cause: The repository upgrade component-specific software module encountered an error while trying to obtain version and status information for the component. This is an internal error.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00049: unable to connect to the source database

Cause: Repository upgrade was unable to connect to the source database instance. The database might be down, or the password might be incorrect.

Action: Verify that the source connect string, user name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00050: unable to connect to the target database

Cause: Repository upgrade was unable to connect to the target database instance. The database might be down, or the password might be incorrect.

Action: Verify that the target connect string, user name, and password are correct. Verify that the database server and listener are running. Examine the log file for additional information.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00101: unable to retrieve password for {0} schema

Cause: Oracle Portal repository upgrade component-specific software module encountered an error while fetching Oracle Portal password from Oracle Internet Directory.

Action: Verify that the Oracle Internet Directory associated with Oracle Portal is up and running and the Oracle Portal password within the Oracle Internet Directory is accessible. After making sure that Oracle Internet Directory is accessible, retry the upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00102: Oracle Portal {0} upgrade log files available in {1}.

Cause: The location of Oracle Portal repository upgrade logs was generated by the Oracle Portal component-specific software module. This is an informational message.

Action: No action is needed.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00103: cannot find Perl in the Oracle home

Cause: Perl was missing from the Oracle home.

Action: Verify that the Oracle home where you are running th Assistant contains the Perl executable.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00104: failure during the Oracle Portal {0} run

Cause: An error occurred either during Oracle Portal precheck run or upgrade run.

Action: Contact Oracle Support Services with the log file details.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00105: failure with progress bar during the upgrade phase of Oracle Portal

Cause: An unexpected error was encountered updating the progress bar.

Action: The Oracle Portal component upgrade was not impacted and the error can be ignored.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00201: missing 10g Entry in SCHEMA_VERSION_REGISTRY

Cause: Oracle Internet Directory schema details were not found in the SCHEMA_VERSION_REGISTRY table.

Action: Refer to the Upgrade Guide for Oracle Identity Management for steps to perform the OID upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00202: The upgrade is not supported from a schema version of {0}.

Cause: An unsupported base schema version was being upgraded.

Action: Refer to the Upgrade Guide for Oracle Identity Management for supported versions for upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00203: failure retrieving ODSSM schema password

Cause: There is no LDAP attribute entry for the ODSSM schema password.

Action: Create 'orclPasswordAttribute' in the Oracle Internet Directory with ODSSM schema password under entry: 'cn=dsaconfig,cn=configsets,cn=oracle internet directory' for upgrade to work.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00204: failure during upgrade precheck: {0}

Cause: Error occurred during the Oracle Internet Directory upgrade precheck.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00205: The ODS schema upgrade is INVALID.

Cause: Some of the packages in the Oracle Internet Directory schema were INVALID after upgrade.

Action: To see which objects are invalid, log in to the Database as user 'ODS' and execute 'select object_name from user_objects where status='INVALID' '. Restore the backed up database and correct the schema before running the Assistant again.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00206: error during Oracle Internet Directory upgrade: {0}

Cause: An unexpected error occurred during Oracle Internet Directory Upgrade.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00207: Error getting OID Component name and ASInstance name

Cause: Unable to get values from 11g opmn.xml

Action: 1. Check that 11g OPMN is running 2. Check that $ORACLE_INSTANCE/config/OPMN/opmn/opmn.xml exists 3. Contact Oracle Support Services if the above steps do not help you resolve the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00208: Could not read details from OID subregistrysubentry

Cause: An error occurred while reading entries from 10g OID

Action: 1. Make sure 10g OID is up and running 2. Contact Oracle Support Services if the above steps do not help you resolve the problem

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00209: error while contacting Oracle Internet Directory: {0}

Cause: unable to connect to the Oracle Internet Directory server. See the exception details for exactly what happened.

Action: 1. Check that Oracle Internet Directory is running. 2. Check that the Oracle Internet Directory connection details are correct in preceding messages in this log.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00210: exception during LDAP schema upgrade : {0}

Cause: Check the preceding messages in this log for detailed cause.

Action: 1. Check the preceding messages in this log for the specific problem. 2. Ensure that the Oracle Internet Directory server is up. 3. Ensure that the Oracle Internet Directory connection credentials are correct. 4. Contact Oracle Support Services if the above steps do not resolve the problem.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00211: error during Oracle Internet Directory schema upgrade: {0}

Cause: An error in SQL processing was detected during Oracle Internet Directory schema upgrade.

Action: Check the SQL messages in $ORACLE_HOME/upgrade/logs/ua<timestamp>.out for the problem and correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00212: error during Oracle Internet Directory schema validation: {0}

Cause: An error occurred during validation of the ODS schema.

Action: 1. Check if Database is running. 2. Check the preceding messages in this log for any errors. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00213: error starting Oracle Internet Directory server with retained ports

Cause: An unexpected error occurred while setting Oracle Internet Directory ports to their 10g values.

Action: Check the preceding messages in this log for detailed cause.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00214: error trying to start the Oracle Internet Directory server: {0}

Cause: An unexpected error occurred when trying to restart the Oracle Internet Directory server after the schema upgrade. See the detailed message at $OI/diagnostics/logs/OID/<oid_comp_name>/oidmon*.log

Action: 1. Check that OPMN is running. 2. Check whether Oracle Internet Directory was already running 3. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00215: Error connecting to database: {0}

Cause: An error occurred when trying to contact/connect to Oracle Database

Action: 1. Check that Database is running. 2. Check the preceding messages in this log for any errors. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00216: Error reading {0} value from {1} file

Cause: An error occurred when trying to read a value from the specified file.

Action: 1. Check that the specified file exists and is readable. 2. Check the preceding messages in this log for any errors. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00217: Error writing {0} value to {1} file

Cause: An error occurred when trying to write a value to the specified file.

Action: 1. Check that the specified file exists and is write-enabled. 2. Check the preceding messages in this log for any errors. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00218: Missing value for {0} in the {1} file

Cause: An error occurred when trying to read a value from the specified file.

Action: 1. Add the missing value in the specified file and retry. 2. Check the preceding messages in this log for any errors. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00219: Error deleting the {0} file

Cause: An error occurred when trying to delete the specified file.

Action: 1. Manually delete the specified file and your upgrade is complete. 2. Check the preceding messages in this log for any errors. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00220: Error updating registration details of OID in WLS: {0}

Cause: An error occurred when trying to run 'opmnctl updatecomponentregistration' for OID.

Action: 1. Check the preceding messages in this log to see if the WLS server details are right. 2. Check if the WLS server is up and running. 3. Check the preceding messages in this log for any errors. 4. Manually run $Oracle_Instance/bin/opmnctl updatecomponentregistration for OID at the end of upgrade. 5. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00221: Error finding OID MBean in WLS: {0}

Cause: An error occurred when trying to find OID Mbean 'oracle.as.management.mbeans.register:instance=<instName>,Location=AdminServer,name=<oidCompName>,type=component' in WLS.

Action: 1. Check the preceding messages in this log to see if the WLS server details are right. 2. Check if the WLS server is up and running. 3. Check the preceding messages in this log for any errors. 4. Manually register OID component in WLS after upgrade. Refer to the OPMN documentation for the same. 5. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00222: error trying to stop the Oracle Internet Directory server: {0}

Cause: An unexpected error occurred when trying to stop the Oracle Internet Directory server after the schema upgrade. See the detailed message.

Action: 1. Check that OPMN is running. 2. Check whether Oracle Internet Directory was already stopped 3. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00223: error trying to start the Oracle Process Manager(OPMN): {0}

Cause: An unexpected error occurred when trying to start the Oracle Process Manager after the schema upgrade. See the detailed message at $OI/diagnostics/logs/OPMN/opmn/opmn.log

Action: 1. Check that OPMN port is not occupied. 2. Check whether OPMN was already running 3. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00224: error trying to add configset entry to OID: {0}

Cause: An unexpected error occurred when trying to add configset entry to OID using oidctl. See the detailed message at $OI/diagnostics/logs/OID/<oid_component_name>/oidctl.log

Action: 1. Check that oidctl binary is present under $OH/bin directory. 2. Verify that the connectstring used in oidctl syntax is the same as the one in $OI/config/tnsnames.ora file. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00225: Error trying to set the SSL properties in the new 11g configset entry of OID: {0}

Cause: An unexpected error occurred when trying to add ssl properties to OID.

Action: 1. Check that orclsslwalleturl attribute value is a valid path. 2. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00301: Unknown technology.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00302: Target Master Repository is invalid.

Cause: Target Master Repositority wasn't found in the given schema.

Action: Define valid Target Master Repository credentials.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00303: Target Work Repository {0} is invalid.

Cause: Target Work Repositority wasn't found in the given schema.

Action: Define valid Target Work Repository credentials.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00304: Target Master Repository is not clone.

Cause: Target and Source Master Repositories are the same.

Action: Make clone of Source Master Repository.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00305: Target Work Repository {0} is not clone.

Cause: Target Work Repository and Source Master Repositories are the same.

Action: Enter correct credentials for Target Work Repository.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00306: Target Work Repository {0} is not clone.

Cause: Target Work Repository has the same schema as Sourcer Work Repository.

Action: Enter correct credentials for Target Work Repository.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00307: More than one Target Work Repository has the same credentials as Target Master Repository.

Cause: Only one Target Work Repository is allowed to have the same credentials as Target Master Repository.

Action: Enter correct credentials for Target Work Repositories.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00308: Target Work Repository {0} must have the same credentials as Target Master Repository.

Cause: Wrong Target Work Repository has the same credentials as Target Master Repository.

Action: Enter correct credentials for Target Work Repository.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00309: Same Target Work Repositories credentials

Cause: Two or more Target Work Repository have the same schema name.

Action: Enter correct credentials for Target Work Repositories.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00310: Target Work Repository {0} has the same credentials as Target Master Repository.

Cause: Source Master Repository doesn't host Work Repository.

Action: Check credentials for Target Work Repository.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00311: Folder with 11g KM is not available

Cause: Folder oracledi/xml-reference/ doesn't exist

Action: Check you ODI Home folder.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00312: Target and Source Master Repositories has the same connection string.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00313: Target Work Repository {0} is hosted in Target Master Repository.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00314: Source Work Repository {0} is hosted in Source Master Repository.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00315: Target Master Repository upgrade is started.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00316: Target Work Repository {0} upgrade is started.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00317: Repository validation.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00318: Getting work repositories.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00319: Getting Original Master Repository connection information.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00320: KM replacing is selected.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00321: Topology upgrade is selected.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00322: Looking for KM {0}.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00323: KM {0} was found.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00324: Topology and Security Metadata upgrade failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00325: Target Master Repository upgrade failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00326: Target Work Repository upgrade failed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00327: Invalid credentials for ODI Supervisor.

Cause: A wrong credentials were provided to upgrade Master and Work Repositories.

Action: Enter correct credentials for ODI Supervisor.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00328: Target Work Repository {0} is invalid.

Cause: Target Work Repositority doesn't belong to Master Repository.

Action: Define valid Target Work Repository credentials.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00329: Can not connect to Master Repository.

Cause: A wrong credentials were provided to upgrade Master Repository.

Action: Define valid Master Repository credentials.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00330: Can not connect to Work Repository.

Cause: A wrong credentials were provided to upgrade Work Repository.

Action: Using Topology Navigator, define valid Work Repository credentials.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00331: Master Repository has invalid state.

Cause: Previous upgrade of Master Repository was unsuccessful.

Action: Restory Master Repository from Backup and try to upgrade again.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00332: Work Repository has invalid state.

Cause: Previous upgrade of Work Repository was unsuccessful.

Action: Restory Work Repository from Backup and try to upgrade again.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00333: Unknow error happened.

Cause: Unknow error happened.

Action: Restory Master Repository from Backup and try to upgrade again.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00334: Unknow error happened.

Cause: Unknow error happened.

Action: Restory Work Repository from Backup and try to upgrade again.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00335: ODI schema "{0}" does not contain a valid ODI repository.

Cause: Master Repositority wasn't found in the given schema.

Action: Define valid Master Repository credentials.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00336: ODI schema "{0}" does not contain a valid 11g ODI repository.

Cause: 11g Master Repositority wasn't found in the given schema.

Action: Please use ODI Upgrade Assisant to perform the upgrade operation from current version to 11.1.1.6.0.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00337: ODI Master schema version found is "{0}".

Cause: ODI PSA is meant for upgrade of ODI repository from 11.1.1.3.0 to 11.1.1.6.0 only.

Action: Please use ODI Upgrade Assisant to perform the upgrade operation from current version to 11.1.1.6.0.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00338: User "{0}" has insufficient privileges.

Cause: DBA user doesn't have SYSDBA privilege.

Action: Try to use user with SYSDBA privilege.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00339: Grant execute in dbmsd_lock failed

Cause:

Action:

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00340: Grant operation failed for schema "{0}".

Cause: Cannot grant execute on dbms_lock to the schema .

Action: Check credentials for Target Work Repository.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00401: The BIPublisher {0} run has an error. {1}.

Cause: An error occurred either during BIPublisher precheck run or upgrade run.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00402: unable to get target schema prefix

Cause: 11g schema prefix is not provided.

Action: Enter value for option '-schemaPrefix' while invoking the upgrade utility.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00403: 10g schema for BIPublisher does not have VALID status in SCHEMA_VERSION_REGISTRY

Cause: The BIPublisher 10g schema version registry entry is invalid.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00404: 11g schema for BIPublisher does not have VALID status in SCHEMA_VERSION_REGISTRY.

Cause: The BIPublisher 11g schema version registry entry is invalid.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00405: The table {0} does not exist.

Cause: The upgrade assistant could not find the table.

Action: Check the upgrade assistant has access to the table.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00406: Error: A SQL error occured during the migration.

Cause: Perhaps the tablespace or log file is full.

Action: Notify your DBA. If unable to resolve, contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00407: Error: Database connections for 10g and 11g are not the same type.

Cause: The database types must be the same (i.e., migrating from DB2 to Oracle is disallowed).

Action: Ensure both database connections are of same type.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00408: Error: Table {0} does not exist in 10g instance.

Cause: Perhaps the scheduler was not installed under this database account.

Action: Ensure that the appropriate database account is specified.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00409: Error: Table {0} does not exist in 11g instance.

Cause: Perhaps the scheduler was not installed under this database account.

Action: Ensure that the appropriate database account is specified.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00410: Error: Failed to create connection for user {0} using connection string {1}.

Cause: The username, password, or other connection information was incorrect.

Action: Provide the correct connection information.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00501: Directory {0} does not exist.

Cause: The upgrade directory is required for the upgrade task to proceed.

Action: Create the directory shown in the error and retry.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00502: No zip file is found for import in {0}.

Cause: A required zip file was missing from the specified upgrade directory.

Action: Run the export utility on 10.1.2 and copy the zip file to the upgrade directory.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00503: error during the {0} phase of Oracle B2B upgrade

Cause: An error occurred either during Oracle B2B precheck run or upgrade run.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00504: MDS configuration exception is detected during Oracle B2B upgrade: {0}.

Cause: During the Oracle B2B schema upgrade an MDS configuration exception was detected. Refer to the secondary error message for details about the cause of the failure.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00505: MDS exception is detected during Oracle B2B upgrade: {0}.

Cause: During the Oracle B2B schema upgrade an MDS exception was detected. Refer to the secondary error message for details about the cause of the failure.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00506: No files are found for import in {0}.

Cause: A required .zip file was missing from the specified upgrade directory.

Action: Run the export utility on 10.1.2 and copy the zip file to the upgrade directory.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00507: MDS transfer fails due to secondary error {0}.

Cause: An error occurred while transferring data from MDS. Refer to the secondary error message for details about the cause of the failure.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00602: Error while retrieving tablespace for OAAM Upgrade.

Cause: Unable to retrieve tablespace of Schema indexes.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00603: SQL error.

Cause: JDBC error while executing query

Action: Make sure DB is reachable and configured properly

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00604: An unknown error occured.

Cause: Unknown

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00701: The Discoverer {0} run has an error. {1}.

Cause: An error occurred either during Discoverer precheck run or upgrade run.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00702: unable to get target schema prefix

Cause: 11g schema prefix is not provided.

Action: Enter value for option '-schemaPrefix' while invoking the upgrade utility.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00703: 10g schema for Discoverer does not have VALID status in SCHEMA_VERSION_REGISTRY

Cause: The Discoverer 10g schema version registry entry is invalid.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00704: 11g schema for Discoverer does not have VALID status in SCHEMA_VERSION_REGISTRY.

Cause: The Discoverer 11g schema version registry entry is invalid.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00705: Discoverer 10g database objects are not available or not in a valid state.

Cause: Discoverer 10g database objects were not available or not in a valid state.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00706: Discoverer 11g database objects are not available or not in a valid state.

Cause: Discoverer 11g database objects were not available or not in a valid state.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00707: Discoverer 10g metadata record with key {0} is corrupt. {1}.

Cause: Specified Discoverer 10g metadata record is corrupt.

Action: Delete the corrupted record and rerun metadata repository upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00801: error during the Oracle BAM {0} run

Cause: An error occurred either during Oracle BAM precheck run or upgrade run.

Action: Contact Oracle Support Services with the log file details.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00802: Oracle BAM precheck failure

Cause: An error occurred during Oracle BAM precheck run.

Action: Contact Oracle Support Services with the log file details.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00803: Oracle BAM upgrade failure

Cause: An error occurred during Oracle BAM upgrade run.

Action: Contact Oracle Support Services with the log file details.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-00804: Oracle BAM precheck success

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00805: Oracle BAM upgrade success

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00806: Oracle BAM is already upgraded

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00807: Oracle BAM is already upgraded.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-00808: Oracle BAM OC4J is running. Stop the Oracle BAM OC4J application and retry the upgrade.

Cause: Oracle BAM OC4J was running.

Action: Oracle BAM OC4J instance is running. Stop the Oracle BAM OC4J and retry the upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00809: The Oracle BAM schema is not a valid 10.1.3 schema.

Cause: The Oracle BAM database schema was not a valid 10.1.3 schema.

Action: Ensure that the Oracle BAM schema is a version 10.1.3 schema.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00901: Failed to update the rule Dictionary at {0}

Cause: Error occured while trying to update dictionary

Action: Moved the composite to Partially_Upgraded_Composites. Upgrade the composite manually.

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00902: Invalid arguments are passed.

Cause: Invalid arguments are passed

Action: Moved the composite to Partially_Upgraded_Composites. Upgrade the composite manually.

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00903: Failed to create a template project at {0}

Cause: Error occured while creating the template BPEL composite

Action: Upgrade the Approval process manually.

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00904: Invalid target type {0} encountered.

Cause: Invalid target type is encountered while generation of rules in BPEL composite.

Action: Moved the composite to Partially_Upgraded_Composites. Upgrade the composite manually.

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00905: Rule with rule key {0} is not default rule.

Cause: The Approval process contains only a single rule which is not default rule.

Action: Moved the composite to Partially_Upgraded_Composites. Upgrade the composite manually.

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00906: Failed to retrieve user login for the user with key {0}

Cause: Error in retrieving user details from the database.

Action: Moved the composite to Partially_Upgraded_Composites. Upgrade the composite manually.

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00907: Failed to retrieve group name for the group with key {0}

Cause: Error in retrieving group details from the database.

Action: Moved the composite to Partially_Upgraded_Composites. Upgrade the composite manually.

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00908: Approval Task is associated with a custom adapter

Cause: {0} is associated with a task assignment adapter

Action: {0} : Implement the task assignment logic in corresponding BPEL Composite.

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00909: Callback URL cannot be set

Cause: Cannot set the callback url in file {0}

Action: Set the Callback URL manually in the file {0}

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00910: Error in parsing the xml file

Cause: Cannot parse the xml file : {0}. Cause : {1}

Action: Upgrade the process manually

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00911: Error in writing parsed XML Document to File

Cause: Error in writing parsed XML Document to File : {0}. Cause : {1}

Action: Upgrade the process manually

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00912: Rule construction is based on Task information.

Cause: Task Information unavailable for rule creation

Action: Update the payload with task information and upgrade the process manually.

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-00921: Error while connecting to the target database.

Cause: DB is not reachable

Action: Make sure DB is up and running and reachable

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00922: OIM ADT constarint is violated

Cause: OIM ADT constarint is violated

Action: Verify OIm schema

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00923: Unable to locate the file. Check logs for more details.

Cause: Unable to find file

Action: Make sure path is correct

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00924: SQL error [{0}]

Cause: JDBC error while executing query

Action: Make sure DB is reachable and configured properly

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-00925: An unknown error occured [{0}]

Cause: Unknown

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01001: unexpected upgrade exception

Cause: An unexpected error occurred while a component was being examined or upgraded.

Action: Check the log file for more details and contact Oracle Support Services, if needed.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01101: exception while backing up file {0}

Cause: Errors occurred backing up the specified configuration file during mod_plsql upgrade.

Action: See the secondary error message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01102: exception while upgrading mod_plsql

Cause: Errors occurred while upgrading one of the mod_plsql configuration files.

Action: See the secondary error message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01103: exception while replacing source Oracle home references in: {0}

Cause: Errors occurred while replacing the Oracle home references in the specified configuration file.

Action: See the secondary error message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01104: exception while copying file {0} to {1}

Cause: Errors occurred copying the specified configuration file.

Action: See the secondary error message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01105: File {0} does not exist in the target instance.

Cause: The specified configuration file for the destination instance was not found.

Action: See the secondary error message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01106: failure to remove obsolete configuration properties from {0}

Cause: Errors occurred removing obsolete properties from the specified configuration file.

Action: See the secondary error message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01201: exception during the upgrade of Oracle Portal

Cause: Oracle Portal upgrade failed while upgrading one of the Oracle Portal configuration files.

Action: See the secondary error message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01202: File {0} does not exist in the destination Oracle instance.

Cause: The specified Oracle Portal configuration file was not found in the destination Oracle instance.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure. Ensure that the configuration file is present in the destination Oracle instance.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01203: Oracle Portal upgrade completed with errors.

Cause: Errors were encountered during the Oracle Portal component upgrade.

Action: Check the OFM Upgrade Assistant log file for details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01204: The default location {0} of the log directory has changed in file {1} of the source Oracle home.

Cause: The default location of log directory has changed in the given file in the source Oracle home.

Action: Check the value of log directory in the destination instance for the given file. Change it to point to the correct location if required.

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-01231: unable to copy file: {0}

Cause: The Oracle JPDK upgrade failed to copy the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01232: unable to create the directory: {0}

Cause: The Oracle JPDK upgrade failed to create the specified directory.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01233: unable to upgrade the <preferenceStore> tag from providers.xml file: {0}

Cause: The Oracle JPDK upgrade failed to migrate some of the provider configurations from the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure. Rerun the middle-tier upgrade after fixing the cause or migrate the configuration manually from the source Oracle home to the destination instance home.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01234: unable to upgrade Provider Group changes from source to destination iasProviders.xml file: {0}

Cause: The Oracle JPDK upgrade failed to migrate the Provide Group changes from the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure. Rerun the middle-tier upgrade after fixing the cause or migrate the configuration manually from the source Oracle home to the destination instance home.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01235: unable to upgrade JNDI entries from source to destination orion-web.xml file: {0}

Cause: The Oracle JPDK upgrade failed to migrate the JNDI entries from the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure. Rerun the middle-tier upgrade after fixing the cause or migrate the configuration manually from the source Oracle home to the destination instance home.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01236: unable to upgrade the Provider UI Security Settings Registry file: {0}

Cause: The Oracle JPDK upgrade failed to migrate the specified Provider UI Security registry file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure. Rerun the middle-tier upgrade after fixing the cause or migrate the configuration manually from the source Oracle home to the destination instance home.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01237: Arguments passed for Oracle JPDK upgrade are illegal.

Cause: The arguments passed to the Oracle JPDK upgrade were incorrect.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure and rerun the middle-tier upgrade after fixing the cause of the error.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01238: No Namespace URI is present for the file {0}.

Cause: The Namespace URI is missing in the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure and rerun the middle-tier upgrade after fixing the cause of the error.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01239: unable to create cache.xml at {0}

Cause: The Oracle JPDK upgrade failed to create the cache.xml file at the specified location in the destination instance home.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure and rerun the middle-tier upgrade after fixing the cause of the error.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01240: failure creating invalidation entries for cache.xml

Cause: The Oracle JPDK upgrade failed to create the invalidation entries in the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure and rerun the middle-tier upgrade after fixing the cause of the error.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01241: failure while trying to obfuscate an authorization attribute in {0}

Cause: The Oracle JPDK upgrade failed to obfuscate the authorization attributes in the specified configuration file.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure and rerun the middle-tier upgrade after fixing the cause of the error.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01242: exception during Oracle JPDK upgrade

Cause: The Oracle JPDK upgrade failed while upgrading one of the configuration files.

Action: See the secondary error message in the OFM Upgrade Assistant log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01271: OmniPortlet is unable to upgrade proxy settings.

Cause: The OmniPortlet upgrade failed to upgrade proxy settings.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01272: OmniPortlet is unable to upgrade customizations.

Cause: The OmniPortlet upgrade failed to copy the portlet customizations from the source Oracle home to the destination instance.

Action: Check the write permissions of the customization directory in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01273: OmniPortlet is unable to upgrade Locale Personalization Level.

Cause: The OmniPortlet upgrade failed to copy the Locale Personalization Level from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01275: OmniPortlet is unable to upgrade the encodeHtmlField setting.

Cause: The OmniPortlet upgrade failed to copy the encodeHtmlField setting from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01276: OmniPortlet is unable to upgrade the exportConnectionInfo setting.

Cause: The OmniPortlet upgrade failed to copy the exportConnectionInfo setting from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01277: OmniPortlet is unable to upgrade Security Repository settings.

Cause: The OmniPortlet upgrade failed to copy the Security Repository settings from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01278: OmniPortlet is unable to upgrade Preference Store settings.

Cause: The OmniPortlet upgrade failed to copy the Preference Store settings from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01279: Web Clipping is unable to upgrade Trusted Certificate Location.

Cause: The Web Clipping upgrade failed to copy the Trusted Certificate Location from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01280: Web Clipping is unable to upgrade Proxy settings.

Cause: The Web Clipping upgrade failed to copy the Proxy settings from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01281: Web Clipping is unable to upgrade translated URL-service providers.

Cause: The Web Clipping upgrade failed to copy the URL-service provider definition files from the source Oracle home to the destination instance.

Action: Check the OFM Upgrade Assistant log file for details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01282: Web Clipping is unable to upgrade Oracle Web Cache settings.

Cause: The Web Clipping upgrade failed to copy the Oracle Web Cache settings from the source Oracle home to the destination instance.

Action: Check the write permissions of $ORACLE_HOME/portal/conf/cache.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01284: Web Clipping is unable to upgrade Security Repository settings.

Cause: The Web Clipping upgrade failed to copy the Security Repository settings from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01285: Web Clipping is unable to upgrade the database respository schema.

Cause: The Web Clipping upgrade failed to upgrade the database respository schema to the new version.

Action: Ensure that the given database repository URL is correct. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01286: OmniPortlet is unable to upgrade the useThinGraph setting.

Cause: The OmniPortlet upgrade failed to copy the useThinGraph setting from the source Oracle home to the destination instance.

Action: Check the write permissions of provider.xml in the destination instance. Check the OFM Upgrade Assistant log file for other possible causes.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01287: exception during Oracle Portal tools upgrade

Cause: Errors were encountered while running the Oracle Portal tools upgrade.

Action: Check the OFM Upgrade Assistant log file for details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01288: failure to import init-param {0} from source {1}

Cause: Errors occurred importing initialization parameters from the specified configuration file.

Action: See the secondary error message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01301: error parsing file {0}

Cause: An error occurred parsing the specified file.

Action: See the secondary error message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01302: error updating file {0}

Cause: An error occurred updating the specified file.

Action: See the secondary error message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01501: invalid Oracle Internet Directory version for upgrade

Cause: Oracle Internet Directory is not at version 11.1 or later.

Action: Upgrade Oracle Internet Directory before upgrading Oracle Directory Integration Platform.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01502: Oracle Directory Integration Platform is already upgraded.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-01503: unable to connect to the Oracle Internet Directory server

Cause: DIP upgrade needs to communicate with the Oracle Internet Directory server. See detailed preceding message in log for why that was not possible.

Action: Ensure that the Oracle Internet Directory server is running.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01504: A Oracle Directory Integration Platform upgrade parameter is missing.

Cause: A required parameter was not available for Oracle Directory Integration Platform upgrade. This is an internal failure of the OFM Upgrade Assistant.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01505: Oracle Directory Integration Platform upgrade failed in the examine phase.

Cause: The upgrade of Oracle Directory Integration Platform failed while checking for a valid starting configuration.

Action: See the secondary messages for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01506: unexpected error

Cause: An unexpected error occurred while upgrading Oracle Directory Integration Platform.

Action: See the secondary messages for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01507: unexpected error

Cause: An unexpected error occurred.

Action: See secondary message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01508: error during Oracle Directory Integration Platform schema upgrade

Cause: The schema files for the Oracle Directory Integration Platform component might be invalid or corrupt.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01509: error during subscriber upgrade

Cause: Upgrading subscriber schema with invalid file or invalid file content.

Action: The subscriber schema files are not valid. Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01510: error during LDAP operation

Cause: An error occurred while performing an LDAP operation on the Oracle Internet Directory server. See secondary message for more details.

Action: Check that Oracle Internet Directory server is fully operational.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01511: error reading Oracle Directory Integration Platform profile information from file system

Cause: A template profile could not be read from the OH/ldap/odi/conf directory.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01512: error creating profile

Cause: There was an unexpected error while creating an Oracle Directory Integration Platform profile.

Action: See secondary message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01513: invalid parameter for profile creation

Cause: An incorrect parameter was used for template profile creation.

Action: See secondary message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01514: error connecting to database

Cause: Oracle Directory Integration Platform upgrade was unable to connect to the database.

Action: Ensure that the database connect string, user name, and password are correct, and the database and listener are running.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01515: error reading Oracle Directory Integration Platform configuration information from the database

Cause: Incorrect SQL was detected while reading Oracle Directory Integration Platform information. This is a coding error within Upgrade.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01516: error during rootcontext upgrade

Cause: The Oracle Directory Integration Platform schema file had invalid file content.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01517: error importing SSL wallet

Cause: Oracle Directory Integration Platform upgrade was unable to import the SSL wallet from the source Oracle home to the Oracle Directory Integration Platform application node.

Action: See secondary message for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01518: failure to connect to the Oracle Internet Directory server

Cause: The upgrade was unable to connect to an Oracle Internet Directory server, as required.

Action: Ensure that the Oracle Internet Directory server is up and running.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01519: error creating CSF key

Cause: KEY creation for Oracle Directory Integration Platform encountered some error.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01520: error creating data source.

Cause: Failure in data source creation for Oracle Directory Integration Platform.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01702: Unexpected exception occurred during Oracle Web Cache upgrade.

Cause: An unexpected exception occurred.

Action: Check the log file for the cause of this problem.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01703: The source Oracle Web Cache version {0} is not supported for upgrade.

Cause: The source Oracle Web Cache version is not supported for upgrade.

Action: Upgrade the source Oracle Web Cache to a supported version first.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01704: Upgrade exception occurred during Oracle Web Cache upgrade on {0}.

Cause: An exception occurred when upgrading Oracle Web Cache configuration files.

Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01706: The destination Oracle Web Cache version {0} is not supported by this Upgrade Assistant.

Cause: The destination Oracle Web Cache version is not supported for upgrade.

Action: Run the Upgrade Assistant for the destination version.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01721: The local CACHE element cannot be found in the source configuration file.

Cause: The configuration file of the source Oracle Web Cache does not contain the CACHE element for the source Web Cache component.

Action: Check the configuration file of the source Oracle Web Cache.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01722: The local CACHE element cannot be found in the destination configuration file.

Cause: The pre-upgrade configuration file of the destination Oracle Web Cache does not contain a valid CACHE element for the destination Oracle Web Cache.

Action: Check the destination Oracle Web Cache configuration file.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01723: Cannot create URL for {0}.

Cause: Exception occurred when creating configuration file URL object. The file name string is malformed and cannot be parsed.

Action: Check configuration files, and contact Oracle Support Services if needed.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01724: The source configuration file webcache.xml does not exist or is invalid.

Cause: The source configuration file webcache.xml does not exist or is invalid.

Action: Ensure that the source configuration file is valid and Oracle Web Cache 10g can start before running Upgrade Assistant.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01730: Backing up configuration file failed.

Cause: Exception occurred when backing up destination configuration file.

Action: Check destination environment for the cause of this problem.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01731: Cannot read port properties from OPMN or OHS property file.

Cause: The OPMN or OHS port properties file doesn't exist or is invalid.

Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01732: Cannot obtain a free port number for the listening port.

Cause: Cannot obtain a free TCP port number for port number conversion.

Action: Manually modify the port number in Oracle WebCache configuration file after upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01733: Testing TCP port {0} failed: {1}

Cause: Exception occurred when testing the port number.

Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01735: The destination administration port number {0} conflicts with one source listening port. Importing destination administration port failed.

Cause: The destination administration port number conflicts with one source non-admin listening port.

Action: Manually change the administration port number after upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01736: The specified CRL path is not a directory. Migrating CRL files in {0} stopped.

Cause: The CRL path specified in CRLPATH is not a directory.

Action: Check the CRL configuration in source configuration file.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01801: Folder {0} doesn't exist.

Cause: Standalone agent component is not installed

Action: Install standalone agent component.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-01901: failure creating Oracle Reports specific upgrade items

Cause: The Oracle Reports upgrade failed to create Oracle Reports specific upgrade items.

Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01903: unable to create Oracle Reports server component {0}

Cause: The creation of the specified Oracle Reports server component failed.

Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01904: unable to create Oracle Reports bridge component {0}

Cause: The creation of the Oracle Reports bridge component failed.

Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01905: failure during upgrade of file {0}

Cause: The Oracle Reports upgrade failed to upgrade the specified configuration file.

Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01906: unable to upgrade dependent components file {0}

Cause: The Oracle Reports upgrade failed to upgrade a dependent component file.

Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01907: unable to upgrade Oracle Reports element

Cause: The Oracle Reports upgrade failed to upgrade an Oracle Reports element.

Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01908: exception getting FRCOMMON node; FRCOMMON node managed files will not be upgraded

Cause: An exception has occurred getting the FRCOMMON node.

Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01909: exception parsing file {0}

Cause: An exception has occurred parsing a configuration file.

Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-01910: exception upgrading registry entries

Cause: The Oracle Reports upgrade failed to upgrade registry entries.

Action: Check the log file for more details.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02001: unable to complete examination phase for Oracle Single Sign-On midtier upgrade for the given source Oracle home

Cause: The source Oracle home did not have a supported product version. Supported source product version numbers start with either 10.1.2 or 10.1.4

Action: Verify that the source Oracle home slated for upgrade has a supported version number.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02002: unable to complete the examination phase for Oracle Single Sign-On midtier upgrade to Oracle Access Manager for the given destination Oracle home

Cause: The destination Oracle home was not at a supported version. Supported product version numbers start with 11.1.

Action: Select a destination Oracle home that is of a supported version for upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02003: The source Oracle home policy.properties configuration file does not exist.

Cause: Either the source Oracle home is corrupted or a valid path was not provided.

Action: Restore a valid source Oracle home from backup or provide a valid path.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02004: The source Oracle home policy.properties configuration file is not readable.

Cause: The source Oracle home is corrupted.

Action: Restore a valid source Oracle home from backup.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02005: unable to get the Oracle Access Manager logger

Cause: The Oracle Single Sign-On upgrade to Oracle Access Manager could not find an internal resource.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-02006: unable to complete Oracle Single Sign-On upgrade examination phase

Cause: Received an unexpected error while attempting to access the policy.properties configuration file in the source Oracle home.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-02007: Could not connect to the Admin Domain MBean Server

Cause: The connection settings are incorrect or Admin Server is down

Action: Ensure that the Admin Domain MBean server is up and that the connection information is correct

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02009: Source Oracle Single Sign-On Schema is Invalid

Cause: The MBean look-up failed.

Action: Ensure that the Admin Domain MBean server is up and OAM Upgrade Mbean is registered.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02010: Error in osso.conf obfuscation

Cause: osso.conf is not generated properly.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02101: source file {0} is not found

Cause: The specified Discoverer configuration file was not found.

Action: Ensure that the source Oracle home is correctly configured.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02102: destination file {0} is not found

Cause: The specified Discoverer configuration file was not found.

Action: Ensure that the destination Oracle instance is correctly configured.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02103: Discoverer upgrade does not support upgrade from version {0}.

Cause: Discoverer upgrade does not support upgrade from the specified version.

Action: Ensure that the version of the source Discoverer installation is certified to work with the OFM Upgrade Assistant.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02104: Discoverer upgrade does not support upgrade to version {0}.

Cause: Discoverer upgrade does not support upgrade to the specified version.

Action: Ensure that the version of the destination Discoverer installation is certified to work with the OFM Upgrade Assistant.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02105: Discoverer configuration file {0} does not exist.

Cause: The specified configuration file did not exist.

Action: Ensure that the destination Discoverer instance is correctly configured.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02107: Discoverer configuration file {0} appears to be corrupted.

Cause: Specified configuration file was corrupted.

Action: Ensure that the destination Discoverer instance is correctly configured.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02108: Source Oracle home specified is invalid.

Cause: Specified Oracle home was invalid.

Action: Ensure that the source Oracle home is specified correctly.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02109: Destination Discoverer installation is remote.

Cause: Specified destination Discoverer installation (Oracle home) was on a remote host.

Action: Ensure that both source and destination Discoverer installations are on the same host.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02201: Oracle Forms Services upgrade does not support upgrade from version {0}.

Cause: Oracle Forms Services upgrade does not support upgrade from the specified version.

Action: Ensure that the version of the source Oracle Forms Services installation is certified to work with the OFM Upgrade Assistant.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02202: Oracle Forms Services upgrade does not support upgrade to version {0}.

Cause: Oracle Forms Services upgrade does not support upgrade to the specified version.

Action: Ensure that the version of the destination Oracle Forms Services installation is certified to work with the OFM Upgrade Assistant.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02203: invalid section name in the configuration file {0}

Cause: An invalid section name was found in the configuration file.

Action: Correct the application section syntax in the specified configuration file and run the upgrade again.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02205: invalid or missing Oracle Forms Services configuration file {0}

Cause: The specified Oracle Forms Services configuration file was either invalid or missing.

Action: Fix the parent configuration file and run the upgrade again.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02206: Oracle Forms Services is not configured in the source Oracle home {0}.

Cause: Oracle Forms Services was not configured in the source Oracle home so no upgrade of Oracle Forms Services occurred.

Action: No upgrade required for the Oracle Forms Services component.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02208: The source File {0}, does not contain any additional user configuration, it will not be upgraded.

Cause: The specified Oracle Forms Services source file did not contain any additional user configuration. No Oracle Forms Services upgrade is needed.

Action: No Action required.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02210: error reading file {0}

Cause: The specified file is either missing or there was a permission error reading the file.

Action: Ensure that the file exists and the file permissions are correct. Run the upgrade again.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02211: error writing the User entries to file {0}

Cause: An error occurred writing the User entries to the specified file.

Action: Rerun upgrade again.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02212: Source file {0} is already upgraded, it will not be upgraded again.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-02213: Configuration file error while parsing {0}.

Cause: An error occurred while parsing the specified configuration file.

Action: Fix the syntax errors in the configuration file and run the upgrade again.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02214: Permissions problem writing the file, {0}.

Cause: A permissions error occurred while writing the specified configuration file.

Action: Fix the file permissions and run the upgrade again.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02215: error reading the Oracle Forms Services configuration file {0} from the source Oracle home

Cause: An unexpected error occurred while reading Oracle Forms Services configuration file {0} from the source Oracle home.

Action: See secondary message for details to resolve the error.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02218: failure to upgrade Oracle Forms Services configuration file {0}

Cause: An unexpected error occurred during upgrade of the specified Oracle Forms Services configuration file.

Action: See secondary message for details to resolve the error.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02301: unable to parse httpd.conf

Cause: A possible syntax error was encountered in the httpd.conf file.

Action: Inspect httpd.conf for possible syntax errors.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02310: unable to parse the default DMS configuration {0}

Cause: A possible syntax error was encountered in the default DMS configuration file.

Action: Inspect the default DMS configuration file for possible syntax errors.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02351: OHS upgrade failure while upgrading {0}

Cause: An unexpected exception occurred while upgrading the specified OHS configuration file.

Action: Check the OFM Upgrade Assistant log file for more details regarding the cause of this problem.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02352: unable to parse {0}

Cause: A possible syntax error was encountered in the specified configuration file.

Action: Inspect the specified configuration file for possible syntax errors.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02353: unable to retrieve the reference httpd.conf file from 11g instance.

Cause: The download of the httpd.conf file from 11g instance failed.

Action: Ensure that httpd.conf exists in the 11g OHS instance.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02354: unable to upload the upgraded OHS configuration files to the destination 11g instance

Cause: The upload of upgraded OHS configuration files to destination 11g instance failed.

Action: Make sure instance is in place.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02355: The wallet already exists; SSL wallet {0} is not imported.

Cause: The SSL wallet already exists, most likely from a previous upgrade run.

Action: This is not an error. No action is required.

Level: 1

Type: WARNING

Impact: Upgrade

UPGCMP-02356: unable to import the SSL wallet {0}

Cause: An internal error has occurred.

Action: Import the SSL wallet manually after upgrade or contact Oracle Support Services for help.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-02357: unable to import the SSL wallet {0}

Cause: An error occurred importing the specified SSL wallet.

Action: Ensure that the wallet is a valid 10g wallet, and run the upgrade again.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02358: unable to configure the SSL end point for {0}

Cause: An internal error has occurred.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-02359: failure while upgrading an SSLWallet directive.

Cause: An internal error has occurred.

Action: Contact Oracle Support Services.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-02360: unable to write out the upgraded config file {0}.

Cause: An error was encountered while attempting to write to a file.

Action: Ensure that the file exists and is writable.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02361: file I/O error while parsing {0}

Cause: The file was either missing or not readable.

Action: Ensure that the file exists and is readable.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02401: Could not connect to the Admin Edit MBean Server

Cause: The connection settings are incorrect or server is down

Action: Ensure that the Admin Edit MBean server is up and that the connection information is correct

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02402: Could not connect to the Admin Domain MBean Server

Cause: The connection settings are incorrect or server is down

Action: Ensure that the Admin Domain MBean server is up and that the connection information is correct

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02403: The {0} parameter is missing

Cause: A parameter required by the OIF Upgrade Plugin is missing

Action: Ensure that the required parameter is set

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02404: Some required parameters are missing

Cause: One or several parameters required by the OIF Upgrade Plugin are missing

Action: Ensure that all the required parameters are set

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02405: Missing file or directory from OIF 10g install: {0}

Cause: A directory or file from the OIF 10g deployment is missing or not readable

Action: Ensure that the directory or file exists and is readable

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02406: Missing file or directory from OIF 11g install: {0}

Cause: A directory or file from the OIF 11g deployment is missing or not writable

Action: Ensure that the directory or file exists and is writable

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02407: An error occurred during the execution of the {0} OIF Upgrade Item

Cause: An Upgrade Item from the OIF Upgrade plugin failed

Action: Check the logs and fix the error that caused the failure

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02408: Unexpected error occurred during the OIF Upgrade Plugin execution

Cause: An error occurred during OIF Upgrade plugin execution

Action: Check the logs for more information

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02501: OVD upgrade failed.

Cause: An error occurred during OVD Upgrade process.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02502: OVD Registration Error.

Cause: An error occurred while registering OVD.

Action: Ensure that the Weblogic Server is running.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02503: Error deleting the $OI/OVD/tmp.dat file.

Cause: Could not delete the $OI/OVD/tmp.dat file

Action: Manually delete the $OI/OVD/tmp.dat file.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02504: OVD MBean not found.

Cause: Was not able to find the OVD Mbean.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02505: Error migrating 10g server.os_xml to 11g.

Cause: Unable to migrate server.os_xml configuration file.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02506: Error migrating 10g listeners.os_xml to 11g.

Cause: Unable to migrate listeners.os_xml configuration file.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02507: Error migrating 10g adapters.os_xml to 11g.

Cause: Unable to migrate adapters.os_xml configuration file.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02508: OVD Upgrade Exception.

Cause: An I/O error occurred while upgrading listeners.os_xml.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02509: XML Configuration error

Cause: An error occurred while upgrading configuration files.

Action: Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02601: Unable to load OAAM property file {0} from the WebApp at {1}

Cause: An error occurred while loading OAAM upgrade related properties.

Action: Check make sure 10G WebApp is valid and its path is correct.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02602: Unable to get connection to OAAM database

Cause: An error occurred while getting connection to OAAM database.

Action: Check the log file and then verify the database properties.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02604: Error occurred while generating sequence value

Cause: An error occurred while generating sequence.

Action: Check the OAAM database and make sure all the sequences exist.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02605: OAAM CSF Credential already exists for the mapName [{0}] and keyName [{1}]

Cause: OAAM CSF Keys already exist. So not migrating the secret keys from 10G Keystore.

Action: Please delete the CSF Credential using Enterprise Manager and re-run the Middle Tier upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02606: Could not migrate secret key with alias [{0}] from keystore [{1}] to CSF

Cause: An error occurred while trying to migrate secret key from keystore to CSF.

Action: Check the upgrade logs, fix the issue and re-run Middle Tier upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02607: Could not find the CSF MBean with the name [{0}]

Cause: An error occurred while trying to lookup CSF MBean.

Action: Make sure OAAM domain is properly configured and CSF MBeans are properly deployed. Fix those issues and re-run Middle Tier upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02608: Could not open keystore [{0}]

Cause: Could not open keystore.

Action: Make sure the keystore password is valid. Fix those issues and re-run Middle Tier upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02609: Could not find key alias [{0}] in keystore [{1}]

Cause: Could not find key alias in keystore.

Action: Make sure OAAM 10G keystore is properly configured. Fix those issues and re-run Middle Tier upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02610: Could not find retrieve key with alias [{0}] from keystore [{1}]

Cause: Could not retrieve key from keystore.

Action: Make sure the keyalias password is valid. Fix those issues and re-run Middle Tier upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02611: OAAM table VCRYPT_DB_PATCHES does not exist for the specified OAAM schema user name.

Cause: The OAAM table VCRYPT_DB_PATCHES could not be found using the entered credentials.

Action: Make sure you have entered credentials for a valid OAAM database.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02701: WLS/LDAP reports problems

Cause: Error occurred while moving users and groups from the RPD to the identity store.

Action: Users and groups may not be migrated.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02703: Could not decrypt password for {0}

Cause: Error occurred while decrypting a password.

Action: The password will not be upgraded and will need to be entered in EM.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02704: Application role {0} does not exist

Cause: Error occurred while importing RPD groups.

Action: Enterprise group membership and application roles will need to be confirmed in EM.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02705: Repository file not found in : {0}

Cause: Error occurred while copying RPD.

Action: The RPD file must be moved to the expected location.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02706: Unable to create the directory {0}

Cause: Error occurred creating a directory.

Action: Investigate the permissions on the file system.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02707: Expected a single subdirectory under {0}

Cause: Error occurred calculating a file path.

Action: Confirm a single instance is installed.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02708: Could not configure logging (Error creating {0})

Cause: OBIPS could not be configured to log upgrade messages.

Action: The WLS configuration should be examined.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02709: Cannot upgrade an RPD which is in the TEMP directory ({0})

Cause: The source RPD was in the temporary directory.

Action: Move the source RPD to another location.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02710: Error setting application role {0} as child of {1}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02711: Error mapping application role {0} to enterprise group {1}

Cause: Error occurred while importing RPD groups.

Action: The application role will have to be manually assigned to the enterprise group in EM.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02712: Expected {0} Oracle instance, found {1}

Cause: Upgrade Assistant can only import to an 11g installation with a single Oracle instance.

Action: Check that a single instance is installed.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02713: Errors were reported during the catalog upgrade. Please refer to the log file for details.

Cause: Error occurred upgrading the catalog.

Action: Please refer to the log file for details of the errors

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02714: Error creating the app role {0}

Cause: See secondary error message for root cause.

Action: Check the permissions, or copy the item locally.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02715: Error accessing the directory {0}

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02716: Could not rename directory {0} to {1}

Cause: Could not rename the directory.

Action: Check the file permissions.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02717: Cannot copy {0} to a subdirectory of itself ({1})

Cause: Cannot copy a directory to a subdirectory of itself.

Action: Select a source directory which is not in the 11g instance.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02718: The catalog upgrade did NOT complete successfully. Please refer to earlier in this upgrade log file or the OBIPS log files found under {0} for more information.

Cause: OBIPS encountered a fatal error during upgrade of the catalog.

Action: Please refer to the upgrade log file and to OBIPS log files for details of the errors.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02719: Error granting {0} permission to app role {1}

Cause: See secondary error message for root cause.

Action: The permission may need to be granted manually.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02720: RPD migration utility encountered the following fatal error: {0}

Cause: RPD migration utility failed to complete successfully.

Action: Please review the above error messages and take appropriate action.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02721: The Upgrade assistant failed to convert the 10g Administrator user name

Cause: RPD migration utility failed to complete successfully.

Action: Please create an Administrator user in the 10g RPD with an ASCII name.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02722: The Upgrade assistant failed to convert the 10g Administrator password

Cause: RPD migration utility failed to complete successfully.

Action: Please change the 10g RPD Administrator password to an ASCII string.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02723: The Upgrade assistant failed to convert the 11g RPD ecryption password

Cause: RPD migration utility failed to complete successfully.

Action: Please select a different password.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02801: Directory {0} does not exist.

Cause: Non existent directory mentioned.

Action: Please mention a location that is a existing directory.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02802: Directory {0} is not readable.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02803: Directory {0} is not writable.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02804: Target directory {0} must have space >= source directory.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02805: Insufficient arguements passed

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02806: Invalid arguements passed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02807: Invalid source file type passed.

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02808: No valid report file found for upgrade in the source directory

Cause: No valid report file found for upgrade

Action: Please make sure there are valid report files in the source directory.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02901: unable to connect to the SOA server at {0}:{1}

Cause: SOA Connection Details are not correct or the SOA server is down.

Action: Check the SOA connection details, start the SOA server if it is down.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02902: {0} not found. Upgrade cannot Continue

Cause: 9102 Patch detected but {0} not found

Action: Make sure that {0} is present under {1}

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02903: Unable To Connect to target Database

Cause: DB is not reachable

Action: Make sure DB is up and running and reachable

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02904: Unexpected Error

Cause: Unexpected behavior

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02905: SQL error [{0}]

Cause: JDBC error while executing query

Action: Make sure DB is reachable and configured properly

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02906: An unknown error occured [{0}]

Cause: Unknown

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02907: Error while transforming {0} [contents to {1} format]

Cause: Transforming error

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02908: Error while unmarshalling oim-config.xml

Cause: Unmarshalling error

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02909: Error while locating the file {0}

Cause: Unable to find file

Action: Make sure path is correct

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02910: Error while generating {0}

Cause: Error during creation

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02912: An error uccured while upgrading the feature {0}

Cause: Problem in feature upgrade

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02913: Please run Admin and oimserver first to populate MDS , then run feature Upgrade

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02914: {0} location Not valid

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02915: Please perform schema upgrade prior to performing feature upgrade

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02916: Error in loading {0}

Cause: Loading file

Action: Make sure the file is present at the correct location in correct format

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02917: [{0}] Error while while updating the failure state of the feature : [{1}]

Cause: Logging error

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02918: MT Plugin can not be run unless Schema and Feature Upgrade are successful

Cause:

Action:

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02919: Failed to load XML. Unable to find record in

Cause: Record not found

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02920: Error while performing I/O [{0}]

Cause: Error in I/O

Action: Make sure path and format is correct

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02921: Database connection is null

Cause: DB error

Action: Make sure Db is up and running

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02922: Problem in featchin data from {0} table

Cause: DB error

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02923: {0} is null

Cause: Object uninitialized/doesnt exist

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02924: Error while copying the {0} to {1}

Cause: I/O Error

Action: Make sure source file exists, destination is writable, and there is space on disk

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02925: Error in importing {0}

Cause: Import error

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02926: OIM schema is null

Cause: Error - OIm schema found to be null

Action: Verify OIM schema

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02927: Error while creating {0} for {1}

Cause: Unable to create object

Action: Make sure path is correct and there is space on file system

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02928: No record found in {0} table

Cause: Database Table empty

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02929: Error while encrypting data

Cause: Problem with data encryption

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02930: Rollback failed

Cause: Error while rolling back the transaction

Action: See the exception details in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02931: Commit failed

Cause: Error while committing the transcation

Action: See the exception details in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02932: updated status update in {0} failed [for key]

Cause: Error while updating DB Table

Action: See the exception details in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02933: encrypted data update in schema table failed.

Cause: Error while updating encrypted data in schema table

Action: See the exception details in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02934: [{0}] Error while retrieving all the groups information :

Cause: Error while retrieving all the groups information

Action: See the exception details in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02935: Error while retrieving all the organizations information :

Cause: Error while retrieving all the organizations information

Action: See the exception details in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02936: Error while finding user form list

Cause: Error while finding user form list

Action: See the exception details in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02937: Error while closing db resources

Cause: Error while closing db resources

Action: See the exception details in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02938: Error while finding group list

Cause: Error while finding group list

Action: See the exception details in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02939: Error in exporting the files to MDS

Cause: Error while exporting the files to MDS

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02940: Error while parsing

Cause: Error while parsing

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02941: [{0}] error occured in request data set generation

Cause: Error occured in request data set generatio

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02942: Error while finding field label for field :

Cause: Error while finding field label for a field

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02943: Error occured while writing dataset to file

Cause: Error occured while writing dataset to file

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02944: [{0}] error while finding IT resource type

Cause: error while finding IT resource type

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02945: [{0}] error while interacting with data base

Cause: error while interacting with data base

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02946: [{0}] error while creating scheduler task

Cause: error while creating a scheduler task

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02947: Error while converting to xml

Cause: Error while converting to xml format

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02948: SOD Upgrade : Error in checking OIM Version

Cause: Error in version checking while doing SOD upgrade

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02949: Jobs does not exist for the task defintion:

Cause: Jobs does not exist for the given task defintion.

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02950: Unable to seed scheduler data due to configuration problems.

Cause: Unable to seed scheduler data due to configuration problems

Action: Contact System Administrator

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02951: Error while Scheduling the jobs

Cause: Error while Scheduling the jobs

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02952: Error while loading Custom OES polices

Cause: Error while loading Custom OES Polcies

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02953: Error while generating report for feature {0}

Cause: Error while genrating Report

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02954: Error in encoding Lookup Query

Cause: Error while encoding Lookup Query

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02955: [{0}] error while retrieving job paramaters

Cause: error while retrieving job paramaters

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02956: Unable to find source for jobs

Cause: Unable to find source for jobs

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02957: [{0}] error while fetching job keys

Cause: Error while fetching job keys

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02958: Error in obtaining default locale code

Cause: Error while obtaining default locale code

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02959: User Customization Upgrade :Error in updating User Display Name

Cause: Error in updating User Display Name while performing User Customization Upgrade

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02960: User Customization Upgrade :Error in generating display name

Cause: Error in generating display name while performing User Customization Upgrade

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02961: Error in Updating Self registration form changes

Cause: Error in Updating Self registration form changes

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02962: Self Register Form Update: error in parsing [{0}]

Cause: Parsing error during Self Register Form Update

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02963: Error in retrieving the customized search attributes

Cause: Error in retrieving the customized search attributes

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02964: JAXB Error while updating User.xml with search Attributes

Cause: JAXB Error while updating User.xml with search Attributes

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02965: File not Found Error while updating User.xml with search Attributes

Cause: File not Found Error while updating User.xml with search Attributes

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02966: User Customization Upgrade :Error in updating User Common Name

Cause: Error in updating User Common Name while performing User Customization Upgrade

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02967: Error while finding group name

Cause: Error while finding group name

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02968: Error while retrieving organization list

Cause: Error while retrieving organization list

Action: See the exception details in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02969: Exception occured while reading the file {0}

Cause: Exception occured while reading file

Action: Make sure source file exists, destination is writable, and there is space on disk

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02970: Role Name Uniqueness : Error in updating {0}

Cause: Error in updating during Role Name Uniqueness

Action: See the exception details in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-02971: SQL Error while setting user lookup value

Cause: SQL Error while setting user lookup value

Action: See the secondary error message in the log file for the cause of the failure.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05001: The 10g table {0}.{1} does not use the default columns. It cannot be upgraded

Cause: The 10g table metadata must not have been changed.

Action: Select a 10g table with the default columns for upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05002: The schema {0} does not exist.

Cause: The upgrade assistant could not find the schema.

Action: Select a table which contains the schema.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05003: The table {0} does not exist.

Cause: The upgrade assistant could not find the table.

Action: Check the upgrade assistant has access to the table.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05004: The table {0} is not empty.

Cause: Cannot upgrade into a non-empty table.

Action: Provide an 11g schema with empty tables.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05101: Audit Server database schema has already been updated.

Cause: Specified Audit Server database schema has already been updated.

Action: No user action is required.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-05102: Audit Server database schema successfully updated.

Cause: Specified Audit Server database schema was successfully updated.

Action: No user action is required.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-05103: The Audit schema updated is INVALID.

Cause: Specified Audit Server database schema was updated but is invalid.

Action: Restore the Audit Server database from a backup and retry.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05104: Audit Server database schema is valid after update.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-05105: Audit Server database schema update failed.

Cause: Specified Audit Server database schema update failed.

Action: Check the log file and if necessary restore the database from backup.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05106: Updating Audit Server database objects to PS2.

Cause: The Audit Server database schema update script is now running.

Action: This is an informational message. No user action is required.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-05107: A SQL statement failed in Audit Server database schema update.

Cause: A SQL error took place, likely because there are data in the OAAM table. Please note that although created in AS 11gR1 PS1 release, the OAAM table in audit schema is supposed to start being used since AS 11gR1 PS2 release. It is supposed to be empty now.

Action: Please move the existing data out of the OAAM table, for the schema to be upgraded. It is important to ensure that the table definition is consistent with the event definitions in component_events.xml.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05201: Seed data has already been loaded.

Cause: Seed data for specified database schema has already been loaded.

Action: No user action is required.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-05202: Failure during the SDF run: {0}.

Cause: An error occurred during seed data loading stage.

Action: Contact Oracle Support Services with the log file details.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-05203: Error contacting database: {0}.

Cause: An error occurred when trying to contact/connect to Oracle Database.

Action: 1. Check that Database is running. 2. Check the preceding messages in this log for any errors. 3. Contact Oracle Support Services if the above steps do not help resolve the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-05401: Database type {0} is not supported.

Cause: Repository upgrade was run against an unsupported database type.

Action: Run the upgrade against either an Oracle, Microsoft SQL Server or IBM DB2 database.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05402: Upgrade installation files could not be found.

Cause: The SQL files required to perform upgrade could not be found in the Oracle home.

Action: Ensure you are running PSA from a WebCenter Oracle home.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05403: The expected temporary tablespace {0} could not be found.

Cause: A temporary tablespace with the name '[prefix]_IAS_TEMP' needs to exist in the database instance but it could not be found.

Action: Create a user temporary tablespace with the name '[prefix]_IAS_TEMP' using the DB2 command line and rerun PSA.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05501: Oracle Metadata Services schema upgrade is invalid.

Cause: Specified Metadata Services schema was updated but is invalid.

Action: Restore the Metadata Services schema from a backup and retry. Check the error messages in Oracle Metadata service component log files. Correct the problem before running the Assistant again.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05502: The upgrade is not supported from Oracle Metadata Services schema version of {0}.

Cause: An unsupported base schema version was being upgraded.

Action: Refer to the Oracle Metadata Services Upgrade Guide for supported versions to upgrade.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-05503: Oracle Metadata Service schema version {0} is latest one. Upgrade is not required.

Cause: Specified Oracle Metadata Services database schema version is the latest one. Upgrade is not required.

Action: No user action is required.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-05504: Error in upgrading Oracle Metadata Services schema.

Cause: An unexpected error occurred during Oracle Metadata Services schema upgrade.

Action: Check the error messages in Oracle Metadata service component log files. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-05505: Error occurred while verifying the character set in target Metadata Services schema

Cause: Some SQL error occurred while verifying the character set in target Metadata Services schema.

Action: Check the error messages in Oracle Metadata service component log files. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-05506: Error occurred while closing the resources during Metadata Services schema upgrade

Cause: Some error occurred while closing the resources during Metadata Services schema upgrade.

Action: Check the error messages in Oracle Metadata service component log files. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-05507: Error occurred while closing Metadata Services schema upgrade log files.

Cause: An unexpected error occurred while closing Metadata Services schema upgrade log files.

Action: Check the error messages in Oracle Metadata service component log files. Correct the problem before running the Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Upgrade

UPGCMP-06001: BI Platform database schema has already been updated.

Cause: Specified BI Platform database schema has already been updated.

Action: No user action is required.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-06002: BI Platform database schema successfully updated.

Cause: Specified BI Platform database schema was successfully updated.

Action: No user action is required.

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-06003: BI Platform database schema is valid after update.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Upgrade

UPGCMP-06004: The BI Platform database schema updated is INVALID.

Cause: Specified BI Platform database schema was updated but is invalid.

Action: Restore the BI Platform database from a backup and retry.

Level: 1

Type: ERROR

Impact: Upgrade

UPGCMP-06005: BI Platform database schema update failed.

Cause: Specified BI Platform database schema update failed.

Action: Check the log file and if necessary restore the database from backup.

Level: 1

Type: ERROR

Impact: Upgrade