1. Migrating Data for Oracle Fusion Middleware Products from On-Premises to ATP-S Database
  2. Troubleshooting ATP-S Database Migration

3 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.
  • 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.
  • 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.
  • 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.

Parent topic: Troubleshooting ATP-S Database Migration

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.

Parent topic: Troubleshooting Database Migration When Using DMS

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.

Parent topic: Troubleshooting Database Migration When Using DMS

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.

Parent topic: Troubleshooting Database Migration When Using DMS

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;

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.

Parent topic: Troubleshooting Database Migration When Using DMS