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 Internet Directory
  For Oracle Internet Directory, you must perform the premigration task of disabling auto purge, before you migrate data to Oracle Autonomous Transaction Processing-Shared (ATP-S) database.
• Premigration Task for Oracle Identity Manager
  Perform the following premigration task before you migrate data to Oracle Autonomous Transaction Processing-Shared (ATP-S) database for Oracle Identity Manager.
• 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';

• Performing Migration for Oracle Identity and Access Management
  Perform the following steps to migrate data from an on-premises database for Oracle Identity and Access Management products, Oracle Access Manager (OAM) and Oracle Identity Manager (OIM).
• Performing Migration for Oracle Internet Directory
  Perform the following steps to migrate data from an on-premises database for Oracle Internet Directory

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 Internet Directory (OID).

1. Set the following environment variable before restoring registry:

   export UA_PROPERTIES= -Doracle.jdbc.fanEnabled=false

   If you do not set this environment variable, you see the error, SEVERE: attempt to configure ONS in FanManager failed with oracle.ons.NoServersAvailable: Subscription time out.

2. Create wallet for ATP-S database.
   1. Copy wallet files to $OH/network/admin.
   2. Update sqlnet.ora file to point to your wallet location: $OH/network/admin.
   3. Update ojdbc.properties by adding SSL_SERVER_DN_MATCH=yes at the end of the file.
3. Apply the OPatch 32089134 for ua restoreRegistry, and the patches 30540494 and 31676526 applicable to an Autonomous Transaction Processing database, and restore schema version registry to TNS_ADMIN=<OH>/network/admin. For more information, see Applying Patches on Oracle Home in Creating Schemas with the Repository Creation Utility.

   [opc@fmw-atps-3 bin]$ cd <OH>/oracle_common/upgrade/bin
   [opc@fmw-atps-3 bin]$ export ORACLE_HOME=<OH>
   [opc@fmw-atps-3 bin]$ ./ua -restoreRegistry
   Oracle Fusion Middleware Upgrade Assistant 12.2.1.4.0
   
   Enter location of Schema Version Registry backup file:
   <OH>/oracle_common/upgrade/bin/registry.xml
   Restoring from <OH>/oracle_common/upgrade/bin/registry.xml
   
   Enter prefix or * for list:
   schema_prefix
   
   Enter the Database Connect String:
   (host:port/service or host:port:SID or TNS connect string)
   jdbc:oracle:thin:@<ATP_databasename>?TNS_ADMIN=<$OH>/network/admin
   Enter the DBA User Name:
   ADMIN
   Enter the DBA Password:
   <Date> oracle.simplefan.impl.FanManager configure
   Schema Version Registry restored from <OH>/oracle_common/upgrade/bin/registry.xml
   Rows removed: 0. Rows inserted: 6.

4. Update data sources xml files in the <Domain_home>/config/jdbc/ directory:
   • opss-audit-jdbc.xml
   • opss-datasource-jdbc.xml
   • LocalSvcTblDataSource-jdbc.xml
   • opss-auditview-jdbc.xml
   • WLSSchemaDataSource-jdbc.xml

   Replace on-premises database URL in the URL property of the above xml files with ATP-S database as shown below:

   jdbc:oracle:thin:@<entry for tns_alias in tnsnames.ora of wallet>

   For example:

   jdbc:oracle:thin:@(description=(retry_count=20)(retry_delay=3)
   (address=(protocol=<protocol_name>)(port=<port_number>)(host=<host_name>))
   (connect_data=(service_name=<service_name>.adb.oraclecloud.com))
   (security=(ssl_server_cert_dn="CN=adwc.uscom-east-1.oraclecloud.com, OU=Oracle BMCS US, O=Oracle Corporation, L=Redwood City, ST=California, C=US")))

5. Update jps-config.xml and jps-config-jse.xml files:
   1. Navigate to $Domain_home/config/fmwconfig directory.
   2. Replace jdbc.url property with the new connection string in jps-config.xml file.
   3. Replace jdbc.url and audit.loader.jdbc.string property with the new connection string in jps-config-jse.xml file.
   Here, we are providing a sample connection string for ATP-S database as an example.

   "jdbc:oracle:thin:@(description=(retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)
   (host=pwyo5vyh.adb.us-ashburn-1.oraclecloud.com))(connect_data=(service_name=eotvufbvvdwnwko_fmwoid_tpurgent.adb.oraclecloud.com))
   (security=(ssl_server_cert_dn="CN=adwc.uscom-east-1.oraclecloud.com, OU=Oracle BMCS US, O=Oracle Corporation, L=Redwood City, 
   ST=California, C=US")))"

   Note:

   Ensure to replace double quotes (") inside the above sample connection string with " as shown below:

   "jdbc:oracle:thin:@(description=(retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)
   (host=pu77bvpd.adb.us-ashburn-1.oraclecloud.com))(connect_data=(service_name=eotvufbvvdwnwko_fmwatpsim_tp.adb.oraclecloud.com))
   (security=(ssl_server_cert_dn="CN=adwc.uscom-east-1.oraclecloud.com, OU=Oracle BMCS US, O=Oracle Corporation, L=Redwood City,
    ST=California, C=US")))"

6. Copy wallet files from <OH>/network/admin to <Domain_home>/config/fmwconfig/components/OID/config except tnsnames.ora.
7. Update sqlnet.ora to point to the new wallet location: <Domain_home>/config/fmwconfig/components/OID/config.
8. Replace contents of tnsnames.ora in <Domain_home>/config/fmwconfig/components/OID/config with OIDDB=<connect string for service name of ATP-S database>.
   For example:

   OIDDB=(description=(retry_count=20)(retry_delay=3)
   (address=(protocol=tcps)(port=1522)(host=pu77bvpd.adb.us-ashburn-1.oraclecloud.com))
   (connect_data=(service_name=eotvufbvvdwnwko_fmwatpsim_tp.adb.oraclecloud.com))
   (security=(ssl_server_cert_dn="CN=adwc.uscom-east-1.oraclecloud.com, 
   OU=Oracle BMCS US, O=Oracle Corporation, L=Redwood City, ST=California, C=US")))

9. Copy all the wallet files from <Domain_home>/config/fmwconfig/components/OID/config to the all OID instance config locations created before migration.
   For example, if there are two instances then copy from <Domain_home>/config/fmwconfig/components/OID/config to the following locations:

   • <Domain_home>/config/fmwconfig/components/OID/oid1/config replacing tnsnames.ora in this location.
   • <Domain_home>/config/fmwconfig/components/OID/oid2/config replacing tnsnames.ora in this location.
10. Set TNS_ADMIN to <Domain_home>/config/fmwconfig/components/OID/config and startnodemanager.
11. On a separate terminal, set TNS_ADMIN to <Domain_home>/config/fmwconfig/components/OID/config and start the Administration Server.
12. Log in to ATP-S database as ODS user.

    SQL > ALTER PACKAGE OLADD COMPILE;
    SQL > @<OH>/oid/common/sql/oid/scripts/ldapxpkg.sql;

13. Set environment variables and run the cleanup commands.

    Assuming that user has created two oid instances prior to migration: oid1 and oid2, perform the steps shown in the following example:

    [opc@fmw-atps-3 bin]$ export JAVA_HOME=<JAVA_HOME>
    [opc@fmw-atps-3 bin]$ export ORACLE_HOME=<ORACLE_HOME>
    [opc@fmw-atps-3 bin]$ export DOMAIN_HOME=<DOMAIN_HOME>
    [opc@fmw-atps-3 bin]$ export WL_HOME=<Oracle_home>/wlserver
    [opc@fmw-atps-3 bin]$ export
    PATH=$JAVA_HOME/bin:$ORACLE_HOME/bin:$ORACLE_HOME/ldap/bin:$DOMAIN_HOME/bin:$PATH
    [opc@fmw-atps-3 bin]$ export INSTANCE_NAME=oid1
    [opc@fmw-atps-3 bin]$ export COMPONENT_NAME=oid1
    [opc@fmw-atps-3 bin]$ oidctl connect=oiddb cleanup
    [opc@fmw-atps-3 bin]$ oidctl connect=oiddb cleanup
    [opc@fmw-atps-3 bin]$ export COMPONENT_NAME=oid2
    [opc@fmw-atps-3 bin]$ oidctl connect=oiddb cleanup
    [opc@fmw-atps-3 bin]$ oidctl connect=oiddb cleanup

    Note:

    Perform the cleanup two times for each instance. If you face any issues in running oid cleanup, see Issues in running oid cleanup.
14. Use the WLST online command to start oid instance.

    For example:

    start('oid1')

15. Restore the original values of orclpurgeenable using ldapmodify command and the original_purge_config.ldif.

    ldapmodify -p <nonssl_ldap_port> -D cn=orcladmin -w <password> -f original_purge_config.ldif
    

    Example contents of original_purge_config.ldif file:

    dn: cn=changelog purgeconfig, cn=purgeconfig, cn=subconfigsubentry
    changetype: modify
    replace: orclpurgeenable
    orclpurgeenable: 1
    
    dn: cn=general stats purgeconfig,cn=purgeconfig,cn=subconfigsubentry
    changetype: modify
    replace: orclpurgeenable
    orclpurgeenable: 1
    
    dn: cn=health stats purgeconfig,cn=purgeconfig,cn=subconfigsubentry
    changetype: modify
    replace: orclpurgeenable
    orclpurgeenable: 1
    
    dn: cn=perf stats purgeconfig,cn=purgeconfig,cn=subconfigsubentry
    changetype: modify
    replace: orclpurgeenable
    orclpurgeenable: 1
    
    dn: cn=tombstone purgeconfig,cn=purgeconfig,cn=subconfigsubentry
    changetype: modify
    replace: orclpurgeenable
    orclpurgeenable: 1
    
    dn: cn=secrefresh events purgeconfig,cn=purgeconfig,cn=subconfigsubentry
    changetype: modify
    replace: orclpurgeenable
    orclpurgeenable: 1
    
    dn: cn=sysresource events purgeconfig,cn=purgeconfig,cn=subconfigsubentry
    changetype: modify
    replace: orclpurgeenable
    orclpurgeenable: 1
    
    dn: cn=oidstats_config,cn=purgeconfig,cn=subconfigsubentry
    changetype: modify
    replace: orclpurgeenable
    orclpurgeenable: 0
    
    dn: cn=user statistics purgeconfig,cn=purgeconfig,cn=subconfigsubentry
    changetype: modify
    replace: orclpurgeenable
    orclpurgeenable: 1
    
    dn: cn=bindsec stats purgeconfig,cn=purgeconfig,cn=subconfigsubentry
    changetype: modify
    replace: orclpurgeenable
    orclpurgeenable: 1
    
    dn: cn=comparesec stats purgeconfig,cn=purgeconfig,cn=subconfigsubentry
    changetype: modify
    replace: orclpurgeenable
    orclpurgeenable: 1
    
    dn: cn=comparefailure stats purgeconfig,cn=purgeconfig,cn=subconfigsubentry
    changetype: modify
    replace: orclpurgeenable
    orclpurgeenable: 1

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. This step is applicable for all products except Oracle Internet Directory.

1. Log in to the WebLogic console.
2. Under Services, click 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. This step is applicable for all products except Oracle Internet Directory.

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 Server Administration Console, go to Security Realms, select the RealmName, 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.

For Oracle Access Manager, benign error messages are displayed. See Error when restarting servers.

Perform the postmigration steps described in this section only if the default store gets updated to Embedded LDAP provided it was defined to a different Oracle Access Manager (OAM) ID Store before migration.

Before you perform the postmigration tasks, you must restore the schema version registry, update the configuration files, and restart the servers. See Restoring the Schema Version Registry, Updating the Configuration Files, and Starting and Stopping Administration and Managed Servers and Node Manager.

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 Identity Manager (OIM).

1. Log in to Oracle Identity Manager sysadmin console.
2. Create the following configuration properties:
   • Property Name: Hierarchical Attributes Support for Entitlements
   • Keyword: Catalog.HierarchicalAttributesOfEntitlement
   • Value: False
3. Restart the OIM server.

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: