The prerequisites to migrate data from an on-premises database to an Oracle Autonomous Transaction Processing-Shared (ATP-S) database is described in the following sections.

• Database Requirements
  
• Creating Resources
  
• Setting Oracle GoldenGate for Online Migrations
  
• Preparing the Database for Migration
  

Perform the following premigration tasks before you migrate data from an on-premises database to Oracle Autonomous Transaction Processing-Shared (ATP-S) database

• Premigration Task for Oracle Forms
  Perform the following premigration task before you migrate data to Oracle Autonomous Transaction Processing-Shared (ATP-S) database for Oracle Forms.
• Premigration Task for Oracle GoldenGate Veridata
  Perform the following premigration task before you migrate data to Oracle Autonomous Transaction Processing-Shared (ATP-S) databasefor Oracle GoldenGate Veridata.
• Creating a Backup of the Schema Version Registry
  Use the Upgrade Assistant on the on-premises host to create a backup of the existing schema version registry on the on-premises database.
• Creating Migration
  A migration contains the parameter settings for running a migration job with Oracle Cloud Infrastructure database migration.
• Validating a Migration
  Before you can run a job with a migration resource in Oracle Cloud Infrastructure Database Migration, the migration resource must be validated.
• Excluding Unsupported Objects
  You must specify objects to include or exclude from a migration job while you are creating a migration resource.

Perform the following steps to migrate data from an on-premises database, for all Oracle Fusion Middleware products except Oracle Identity and Access Management Suite of products.

1. Run the migration job. For more information, see Running a Migration Job in Using Oracle Cloud Infrastructure Database Migration Service.
2. Pause after the Monitor Replication Lag phase for the transaction replication to continue during the waiting state.
3. Migrate the excluded objects manually using Oracle Data Pump expdp and impdp commands.

   See step 5 in Preparing the Source Database for Migration. For the user privileges, see Table A-1 for each product.

   To create a parameter in the <DB $OH> directory, see Table A-2.

4. Export all schemas at once using the expdp command.
   Example:

   ./expdp ggadmin/<ggadmin_password>@<PDB_connect_string> dumpfile=dump_tables.dmp 
   logfile=<logfilename>.log directory=<DPDIR> parfile=<parfilename>.par full=y

   To export the MDS (Metadata Services) schema individually, run the following command:

   Example:

   ./expdp <schema_prefix>_MDS/<MDS_schema_password>@<PDB_connect_string> directory=<DPDIR> dumpfile=<dumpfilename>.dmp logfile=<logfilename>.log
   parfile=<parfilename>.par

   For the expdp commands for each product, see Table A-3.

5. After the export, for MDS schema, do the following:
   1. Generate sqlfile to validate the contents before executing import on ATP-S.

      impdp <schema_prefix>_MDS/<MDS_schema_password>@<PDB_connect_string> dumpfile=<dumpfilename>.dmp sqlfile=<DPDIR>:<filename>_imp.sql

      where, dumpfilename.dmp is the dump file from the expdp command of MDS schema in step 4.

   2. Execute the SQL command as a SYS or ggadmin user in PDB.

      sqlplus > select dbms_metadata.get_ddl('TABLE','TABLE_NAME','<schema_prefix>_MDS') from dual;

      Note:

      Verify the results of the above query with the contents of <filename>_imp.sql in /u01/app/oracle/product/19.0.0.0/dbhome_1/rdbms/log/<DPDIR>. Both the results must be same.
6. Upload the dumpfile into cloud object storage and copy the path.
7. Import the data dump file to an ATP-S database for your schemas.
   1. Set the following environment variables on the Oracle Cloud Infrastructure (OCI) host on which you have installed your Oracle Fusion Middleware product.

      cd /usr/lib/oracle/21/client64/bin
      export LD_LIBRARY_PATH=/usr/lib/oracle/21/client64/lib:$LD_LIBRARY_PATH
      export PATH=/usr/lib/oracle/21/client64/bin:$PATH
      export TNS_ADMIN=<ATP-S_wallet_location>
      /sqlplus /nolog
      connect admin/<admin_password>@<ATP_databasename>                                                                                                                                                                                                                                                                                                                                                                                                       

   2. Create credentials.

      BEGIN
        DBMS_CLOUD.CREATE_CREDENTIAL(
        credential_name => '<DEF_CRED_NAME>',
        username => '<OCI_Username>',
        password => '<Your_Auth_Token_Here>'
        );
      END;
      /

   3. Remap the tablespaces using the impdp command.
      Example:

      impdp admin/<admin_password>@<ATP_databasename> credential=def_cred_name dumpfile= <dump_file_cloud_object_storage_location>.dmp REMAP_TABLESPACE=<schema_prefix>_SCHEMA:DATA
      REMAP_TABLESPACE=<schema_prefix>_IAS_TEMP:TEMP
      

      For the impdp commands for each product, see Table A-3.

   4. For MDS, test if the MDS purge path table is imported successfully.

      select table_name from dba_tables where owner='<schema_prefix>_MDS' and table_name like 'MDS_PURGE_PATHS';

Perform the postmigration steps described in this section after migrating data from an on-premises database to an Oracle Autonomous Transaction Processing-Shared (ATP-S) database for Oracle Data Integrator (ODI).

1. Connect to the Master repository with valid credentials.
2. To open the work repository, click Topology and then click WORK_REPO.
3. Click Connection Information of the Work repository and update the connection string.
   Example connection string:
   jdbc:oracle:thin:@<<connect_name>?TNS_ADMIN=/home/opc/WalletDB
4. Save and test the connection.
5. In the Login screen, choose the Work repository and proceed with login.

You must rewire the datasources in the Oracle Fusion Middleware domain with the newly created ATP-S target database.

1. Log into the WebLogic Remote Console.
2. Navigate to Services and select Datasources.
3. Update all the data sources connect string with ATP-S database connection string.
   The connect sting format is jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path_of_the_wallet_files, ojdbc.properties, and tnsnames.ora>

Follow the steps in this section to update the config.xml configuration file, and the Oracle Platform Security Services ( OPSS) configuration files, jps-config.xml and jps-config-jse.xml files in the Oracle Cloud Infrastructure Database Migration domain host.

1. To update the config.xml file:
   1. Navigate to the directory, $DOMAINHOME/config on the OCI domain host.
   2. If the RDBMS security store is enabled in the on-premises domain, update the config.xml file in one of the following ways:
      • In the WebLogic Remote Console, navigate to Security > Realms, click RDBMS Security Store and update the RDBMS connection configuration.
      • Use the WebLogic Scripting Tool (WLST).

        Note:

        For sec:connection-url, update jdbc:oracle:thin:@@//dbserver:listener_port/DB_ServiceName with the new database location, jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path_of_the_wallet_files, ojdbc.properties, and tnsnames.ora>.

        Example command to update the config.xml file:

        store = realm.getRDBMSSecurityStore()
        store.setUsername('<Db_SchemaUser>')
        store.setPassword('<Db_SchemaPassword>')
        store.setConnectionURL('jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path_of_the_wallet_files, ojdbc.properties, and tnsnames.ora>')
        store.setDriverName('<driverName>')

        Example of config.xml after update:

        <sec:rdbms-security-store>
            <sec:username><Db_SchemaUser></sec:username>
            <sec:password-encrypted><Db_SchemaPassword></sec:password-encrypted>
            <sec:connection-url>jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path_of_the_wallet_files, ojdbc.properties, and tnsnames.ora>
            <sec:driver-name><driverName></sec:driver-name>
        </sec:rdbms-security-store>

2. To update the jps-config.xml and jps-config-jse.xml files:
   1. Navigate to $DOMAINHOME/config/fmwconfig directory on the OCI domain host.
   2. In the jps-config.xml, replace jdbc.url property with the new connection string.

      jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path_of_the_wallet_files, ojdbc.properties, and tnsnames.ora>

      Example:

      jdbc:oracle:thin:@fmwatpsim_tp?TNS_ADMIN=/home/opc/

   3. In thejps-config-jse.xml, replace jdbc.url and audit.loader.jdbc.string property with the new connection string.
      During migration, if you have changed the OPSS password in your Oracle Autonomous Transaction Processing-Shared (ATP-S) database, execute the following WebLogic Scripting Tool (WLST) commands in offline mode:

      cd <Domain_Home>/oracle_common/common/bin./wlst.sh
      
      Initializing WebLogic Scripting Tool (WLST) ...Jython scans all the jar files it can find at first startup.
      Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.
      Welcome to WebLogic Server Administration Scripting Shell Type help() for help on available commands
      
      modifyBootStrapCredential(jpsConfigFile="<Domain_Home>/config/fmwconfig/jps-config-jse.xml",
      username="<Prefix>_OPSS", password="<New_Password>")

3. Save the changes.

After the migration of your data from on-premises to an Oracle Autonomous Transaction Processing-Shared (ATP-S) database, restart all processes and servers, including the Administration Servers and any Managed Servers.

See Starting and Stopping Administration and Managed Servers and Node Manager in Administering Oracle Fusion Middleware.

After the migration of data from your on-premises to an Oracle Autonomous Transaction Processing-Shared (ATP-S) database, verify the application URLs, and ensure that data is accessible from the application.

After you perform sanity check: