1. Migrating Oracle Fusion Middleware On-Premises Database to an Autonomous Transaction Processing (Dedicated) Database
  2. Troubleshooting an On-Premises Database to an Autonomous Transaction Processing-Dedicated Database Migration

3 Troubleshooting an On-Premises Database to an Autonomous Transaction Processing-Dedicated Database Migration

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

Metadata Error When Exporting Schemas

You might receive a metadata error when you are exporting schemas from an on-premises database using the expdp command..

To fix the issue, perform the following steps:

  1. Set execute permissions on xsl:
    chmod 755 <DB $OH>/rdbms/xml/xsl
  2. Reload the stylesheets using the dbms_metadata_util.load_stylesheets procedure in SQL.
    SQL > execute dbms_metadata_util.load_stylesheets
  3. Restart the database and execute the expdp command again.

Parent topic: Troubleshooting an On-Premises Database to an Autonomous Transaction Processing-Dedicated Database Migration

Errors Postmigration to an Oracle Autonomous Transaction Processing-Dedicated (ATP-D) Database

Troubleshoot the errors you receive after migrating an on-premises database to an Oracle Autonomous Transaction Processing-Dedicated (ATP-D) database.

Error Migrating Schemas

After you migrate an on-premises database to an Autonomous Database for the Oracle Fusion Middleware products, during the migration of JRF schemas, you might receive the following error:ORA-00001: unique constraint (<Schema Prefix>_WLS.SYS_C00522571) violated.

This error is displayed for the following tables:

  • CHECKPOINTDATA;

  • EXECUTIONINSTANCEDATA;

  • JOBINSTANCEDATA;

  • JOBSTATUS;

  • STEPEXECUTIONINSTANCEDATA;

  • STEPSTATUS;

  • WEBLOGIC_TIMERS;

  • WL_SERVLET_SESSIONS;

  • WLS_EVENTS;

  • WLS_HVST;

So, to 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 While Running the Reports Builder

After you migrate an on-premises database to an Autonomous Database, for Oracle Reports, you receive the following error: Error: REP-0004 Text: Warning - "Unable to open user preference file". while running reports.

This warning is displayed if the Oracle Reports executable file is not found in the specified location; the process will continue even if this warning is displayed.

Copy the prefs.ora file from your Reports Builder directory, ORACLE_HOME/tools/admin/ directory to the Applications directory, HOME.

Bind to Reports Server Failed

After you migrate an on-premises database to an Autonomous Database, for Oracle Reports, you receive the following error: REP-51002: Bind to Reports Server rep_server failed.

If you receive this error, you must enable naming service discovery mechanism for all Reports servers in Oracle Reports 14c.

Note:

Ensure that the WLS_REPORTS managed server and Reports server are down.

  1. Create a backup of the rwnetwork.conf files, and then edit the rwnetwork.conf files.

    • $DOMAIN_HOME/config/fmwconfig/components/ReportsToolsComponent/<ReportsToolsInstance>/rwnetwork.conf (Tools)
    • $DOMAIN_HOME/config/fmwconfig/components/ReportsServerComponent/<standalone repserver>/rwnetwork.conf (Standalone Reports Server)
    • $DOMAIN_HOME/config/fmwconfig/servers/WLS_REPORTS/applications/reports_12.2.1/configuration/rwnetwork.conf (In-process Reports Server)

  2. Enable naming service (COS) discovery mechanism for all the updated rwnetwork.conf files.

    For example:

    #From
<multicast channel="228.5.6.7" port="14021" timeout="1000"/>
<!--namingService name="Cos" host="%NAMING_HOST%" port="%NAMING_PORT%"/-->

#To
<!--multicast channel="228.5.6.7" port="14021" timeout="1000"/-->
<namingService name="Cos" host="<your host name>" port="<Port Number>"/>
# Ensure that you specify the port number within the range reserved for the Reports server (14021 to 14030).
  3. Start the naming service process. 
    $DOMAIN_HOME/reports/bin/namingservice.sh <Port_Number>
  4. Start WLS_REPORTS component from the WebLogic Console and the standalone Reports Server: 
    $DOMAIN_HOME/bin/startComponent.sh <standalone_repserver>
  5. Run the following command to verify if Namingservice (COS) discovery mechanism is working fine: 
    $DOMAIN_HOME/reports/bin/rwdiag.sh -findAll

    Note:

    namingService is not supported for Reports server discovery in High Availability setup.

    When you start the Reports server, you receive the following error: XML Parse exception :Element 'namingService' not expected. This error is displayed if the rwnetwork.conf files are not configured correctly with namingService.

Parent topic: Troubleshooting an On-Premises Database to an Autonomous Transaction Processing-Dedicated Database Migration