4 Troubleshooting ATP-S Database Migration

Learn to troubleshoot any issues you might encounter as part of the migration process.

Troubleshooting Database Migration When Using DMS

When you are migrating from other Oracle Databases to Oracle Autonomous Database, refer Notes for Users Migrating from Other Oracle Databases in Using Oracle Autonomous Database on Shared Exadata Infrastructure.

DBA Role Privileges Issue

Migration fails when user is granted DBA privileges as the role used in the source database is not available in the target database and the error ORA-39083: Object type ROLE_GRANT failed to create with error ORA-01924: role 'DBA' not granted or does not exist is displayed.

To fix the role privileges issue, do the following:

  1. Execute the following SQL on the source database:
    revoke <role> from <username>
    Example:
    revoke DBA from FMW
  2. Resume migration on DMS.

Browse Option Fails in OID

In Oracle Internet Directory (OID), when creating a new user if you try to use the browse button to select a path, an unresolvable error might occur.

To resolve this issue, do one of the following:

  • Manually type the path detail and click Next.
  • Use the command-line tool ldapadd to add entries to the directory

Premigration Errors

Troubleshoot the errors you receive during the validation phase, when migrating data from an on-premises database to an Oracle Autonomous Transaction Processing-Shared (ATP-S) database.

For premigration errors displayed during the Validation phase, see Tables B-1, B-2, and B-3 in Oracle GoldenGate Unsupported Objects and Objects in CPAT Tool Errors.

Validation fails for Oracle Text DR$ index table

As the DR$ index tables are secondary objects, you cannot export these objects during migration, but you must export the table with it's index definition (original table). When you import these tables, the index is recreated and the secondary objects are created. So, validation of these objects in the source database fails, in DMS.

As a workaround, exclude the failed DR$ objects from migration before you proceed with the migration process. Postmigration these objects get recreated in the ATP-S database.

Migration Errors

Troubleshoot the errors you receive while migrating data from an on-premises database to an Oracle Autonomous Transaction Processing-Shared (ATP-S) database.

Import log error in Oracle Identity Manager

For Oracle Identity Manager (OIM), the following error is displayed in the import log, and this error can be ignored.

24-NOV-21 15:52:44.782: ORA-39083: Object type
PROCOBJ:"NV6_SOAINFRA"."AQ$_EDN_EVENT_QUEUE_TABLE_V" failed to create with error:
ORA-24166: evaluation context NV6_SOAINFRA.AQ$_EDN_EVENT_QUEUE_TABLE_V has errors"

Import log for Oracle Internet Directory

For Oracle Internet Directory (OID), the following warning is displayed in the import log. This warning is benign and can be ignored.

ORA-39082: Object type PACKAGE BODY:"ODS"."MANAGEHIQ" created with compilation warnings

Postmigration Errors

Troubleshoot the errors you receive after migrating data from an on-premises database to an Oracle Autonomous Transaction Processing-Shared (ATP-S) database.

Error migrating schemas

After you migrate an on-premises database to an ATP-S database for the Oracle Fusion Middleware products, during the migration of WLS schemas, you might receive the following error:"ORA-00001: Unique constraint" Error customer should truncate data from tables.

This error occurs, if the LAST_NUMBER of sequence SEQ_WLS_HVST_RECORDID in source database is greater than LAST_NUMBER of sequence SEQ_WLS_HVST_RECORDID in target database.

To fix the issue, do the following:

  • Alter and restart the sequence with number >= last number in source database.
    SQL> ALTER SEQUENCE <schema_prefix>_WLS.SEQ_WLS_HVST_RECORDID restart start with <<LAST_NUMBER_of_sequence_SEQ_WLS_HVST_RECORDID>;
  • Migrate the schemas, use the following commands in SQL*Plus to truncate data from the WebLogic Server database tables:
    DELETE from ACTIVE;
    DELETE from CHECKPOINTDATA;
    DELETE from EXECUTIONINSTANCEDATA;
    DELETE from JOBINSTANCEDATA;
    DELETE from JOBSTATUS;
    DELETE from STEPEXECUTIONINSTANCEDATA;
    DELETE from STEPSTATUS;
    DELETE from WEBLOGIC_TIMERS;
    DELETE from WL_SERVLET_SESSIONS;
    DELETE from WLS_EVENTS;
    DELETE from WLS_HVST;

Error restarting the servers

For Oracle Access Manager, the following errors are displayed on restarting the servers. These error messages are benign and can be ignored.

  1. [partition-id: 0] [partition-name: DOMAIN] > <BEA-000000> 
    <Request to processartifacts failed.
    Context=OAM_CONTEXT java.lang.Exception: No file found
    with the name /config/fmwconfig/oauth.xml in database.
    at oracle.security.am.artifacts.store.DBArtifactStore.read(DBArtifactStore.java:191)
    at oracle.security.am.artifacts.processor.DBToFileArtifactProcessor.processRequest(DBToFileArtifactProcessor.java:78)
  2. Context=OAM_CONTEXT
    java.lang.Exception: No file found with the name /config/fmwconfig/oic_rp.xml
    in database.
    at oracle.security.am.artifacts.store.DBArtifactStore.read(DBArtifactStore.java:191)
    at oracle.security.am.artifacts.processor.DBToFileArtifactProcessor.processReques
    t
  3. Context=OAM_CONTEXT 
    <84579d79-4cd7-45bf-b105-a8b08f4c5680-00000009>
    <1632901333560><[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
    <BEA-000000> <Request to process artifacts failed.
    at oracle.security.am.artifacts.store.DBArtifactStore.read(DBArtifactStore.java:191)
    at java.lang.Exception: No file found with the name /config/fmwconfig/idaas.xmlin database.
  4. <528afb44-5de6-464b-b059-0f872e0139ff-00001fbd> <1631015303075>
    <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
    <BEA-000000> <This resource already exists, within domain "testwg".
    oracle.security.am.common.policy.admin.impl.PolicyValidationException:
    OAMSSA-06289: This resource already exists, within domain "testwg".
    at partition-id: 0] [partition-name: DOMAIN]> 
  5. 60098:Faces lifecycle receives unhandled exceptions in phase
    INVOKE_APPLICATION 5 javax.faces.el.EvaluationException: java.lang.NullPointerException
    at <3d56ab11-4a44-4847-a807-ba6dc771f38a-0004e4a3> <1632897060940>
    <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
    <BEA-101017> <[ServletContext@1114167768[app:oam_server module:oam path:null
    spec-version:3.1]]
  6. Root cause of ServletException.
    java.lang.NoClassDefFoundError: oracle/igf/ids/LDAPConnectionException
    at
    oracle.security.am.engines.common.identity.provider.impl.IdentityProviderImpl.
    locateUser(IdentityProviderImpl.java:1468)
    at
    oracle.security.am.engines.common.identity.provider.impl.OracleUserIdentityPro
    vider.locateUser(OracleUserIdentityProvider.java:526)
    at
    84579d79-4cd7-45bf-b105-a8b08f4c5680-00000162> <1632902625446>
    
  7. <[severity-value: 16] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] >
    <ADFC-50023> <ADFc: Attempt to release viewport 'ga1qt8dou_0' threw an
    exception.
    oracle.adf.controller.ControllerException: ADFC-12014: Attempted access to an
    object that has already been released, object type:
    'oracle.adfinternal.controller.state.RootViewPortContextImpl'.
    at
    partition-id: 0] [partition-name: DOMAIN] > <BEA-240003> <Administration
    Console encountered the following error: java.lang.NoSuchMethodError:
    org.glassfish.jersey.internal.LocalizationMessages.WARNING_PROPERTIES()Ljava/l
    ang/String;
    at
    org.glassfish.jersey.internal.config.SystemPropertiesConfigurationModel.getPro
    pe

FirstSiteII not supported for ATP-S database migration

After migrating an on-premises database to an Oracle Autonomous Transaction Processing (ATP-S) database, for Oracle WebCenter Sites, installing and configuring FirstSiteII sample site, and creating and editing a Promotion Asset is not supported.

Issues in running oid cleanup

For Oracle Internet Directory , if you face any errors during cleanup, instead of step 14 in Postmigration Tasks for Oracle Internet Directory, do the following:

  1. Start all existing oid instances created before migration.
  2. Stop all existing oid instances created before migration.
  3. Stop node manager.
  4. Stop the Administration server.
  5. Start the Administration server.
  6. Start the Node manager.
  7. Start all existing oid instances created before migration

Troubleshooting Database Migration When Using Data Pump

Learn to troubleshoot any issues you might encounter when you migrate data for Oracle Identity Governance (OIG) and Oracle Access Manager (OAM) using data pump.

Catalog Search Not Working

In Oracle Identity Governance (OIG), catalog search does not display any results.

To resolve this issue:
  1. Log in to Oracle Identity sysadmin console.
  2. Under System Configuration, click Configuration Properties.
  3. In the left pane of the System Configuration section, from the Actions menu, select Create Alternatively, you can click the create icon on the toolbar.

    The Create System Property page appears.

  4. Enter the following values:
    • Name: Hierarchical Attributes Support for Entitlements
    • Keyword: Catalog.HierarchicalAttributesOfEntitlement
    • Value: false
  5. Click Save.

Unable to Export Large Number of Artifacts From the Sysadmin Console

When Oracle HTTP Server (OHS) server is used at the front end to access web applications, and you retrieve large number of resource entities, such as role artifacts, from the Sysadmin console using the Deployment Manager, the UI times out and does not return any results.

The workaround is to perform the search based on type and name, and limit the results, instead of trying to retrieve all data at once.