There are different methods of cloning a database and each method has its own merits.

You can use the following options to clone the database:

Option 1 – Database Export Import

Option 2 – Duplicate Database Using RMAN

• Suitable for databases of any size.

• Takes a back up of an entire database.

• The database version and patch level should be the same on both the source and destination.

• Database upgrades will need to be performed as a separate task.

• CDP/PDB migration will have to be done as a separate exercise.

• No ongoing synchronization.

• During cut-over, you should freeze the source system for updates.

Option 3 – Data Guard Database

• Suitable for databases of any size.

• Takes a back up of an entire database.

• Database upgrades will need to be performed as a separate task.

• CDP/PDB migration will have to be done as a separate exercise.

• Ongoing synchronisation; Database can be opened to test the upgrade and closed again to keep data synchronized with the source system.

1. Create and set the directory details for the export process on the source DB hosts.
   1. Make a directory on the source DB hosts in a location with sufficient space.

      mkdir -p /u01/installers/database

   2. On the source database, create a database directory object pointing to this location:

      SQL> CREATE DIRECTORY orcl_full AS '/u01/installers/database';

2. Shutdown WebLogic Server Managed Servers or Clusters for OIM, SOA, and BIP.

   Note:

   If executing in parallel with the domain backup, coordinate the shut down of the entire domain including AdminServer and NodeManagers.
3. Stop the SOA DBMS queues in the source database.
   1. Connect as the SOAINFRA schema user and query for the user queues.

      $ sqlplus <PREFIX>_SOAINFRA@<sourceDB>
      SQL> COLUMN name FORMAT A32
      SQL> SELECT name,enqueue_enabled,dequeue_enabled  
      FROM USER_QUEUES where queue_type = 'NORMAL_QUEUE' order by name;
      NAME                             ENQUEUE DEQUEUE
      -------------------------------- ------- -------
      B2B_BAM_QUEUE                     YES        YES
      EDN_EVENT_QUEUE                   YES        YES
      EDN_OAOO_QUEUE                    YES        YES
      IP_IN_QUEUE                       YES        YES
      IP_OUT_QUEUE                      YES        YES
      TASK_NOTIFICATION_Q               YES        YES
      
      6 rows selected.

   2. Stop each queue.

      SQL> BEGIN
      
      DBMS_AQADM.STOP_QUEUE ('B2B_BAM_QUEUE');
      
      DBMS_AQADM.STOP_QUEUE ('EDN_OAOO_QUEUE');
      
      DBMS_AQADM.STOP_QUEUE ('EDN_EVENT_QUEUE');
      
      DBMS_AQADM.STOP_QUEUE ('IP_IN_QUEUE');
      
      DBMS_AQADM.STOP_QUEUE ('IP_OUT_QUEUE');
      
      DBMS_AQADM.STOP_QUEUE ('TASK_NOTIFICATION_Q');
      
      END;
      
      /
      exit

4. As the OIM schema user, query for and stop any running DBMS_SCHEDULER jobs in the source database.

   $ sqlplus <PREFIX>_OIM@<sourceDB>
   
   SQL> SELECT job_name,session_id,running_instance,elapsed_time 
   FROM user_scheduler_running_jobs ORDER BY job_name;
   
   no rows selected

   Note:

   In case of any running jobs, either wait till the job is complete or stop the job ‘gracefully’ using:

   SQL> BEGIN
   
   DBMS_SCHEDULER.stop_job('REBUILD_OPTIMIZE_CAT_TAGS');
   
   END;
   
   /
   SQL> exit

5. Grant system policies to avoid errors during export datapump jobs.

   $ sqlplus SYS as SYSDBA
   SQL> GRANT EXEMPT ACCESS POLICY TO SYSTEM;
   SQL> exit

6. Export the system and application schemas from the source database, setting the directory property appropriately.
   1. Export the system.schema_version_registry table and view:

      $ expdp \"sys/<password>@<sourcedb> as sysdba \" \
           DIRECTORY=orcl_full \
           DUMPFILE=oim_system.dmp \
           LOGFILE=oim_system_exp.log \
           SCHEMAS=SYSTEM \
           INCLUDE= VIEW:"IN('SCHEMA_VERSION_REGISTRY')" TABLE:"IN('SCHEMA_VERSION_REGISTRY$')"\
           JOB_NAME=MigrationExportSys

   2. Export all of the schemas used by the datasources in the source WebLogicServer domain.

      $ expdp \"sys/<password>@<sourcedb> as sysdba \" \
           DIRECTORY=orcl_full \
           DUMPFILE=oim.dmp \
           LOGFILE=oim_exp.log \
           SCHEMAS=<PREFIX>_OIM,<PREFIX>_SOAINFRA,<PREFIX>_BIPLATFORM,<PREFIX>_MDS,<PREFIX>_ORASDPM,<PREFIX>_OPSS,IGDJMS,IGDTLOGS \
           JOB_NAME=MigrationExport \
           EXCLUDE=STATISTICS

7. Extract the source database DDL for the tablespaces, schema users, and grants.

   This step allows the efficient creation of the correct tablespaces on the target database and retains the schema user passwords. Therefore, domain reconfiguration is not necessary. System and Object grants for objects outside the exported schemas are also accounted for to reduce the risk of invalid objects and recompilation difficulties.

   An example script is provided to create the complete SQL DDL output all at once. The example will need to be modified if not using a CDB/PDB.

   1. In SQLPLUS, execute the example SQL script to extract the DDL to a ddl.sql file in the same directory as the datapump exported dumps. Enter the source environment and the target PDB. Output will be copied to both the screen and in the file named ddl.sql.

      $ cd /u01/installers/database
      $ sqlplus SYS as SYSDBA
      SQL> @extract_ddl.sql
      Enter RCU Prefix: <PREFIX>
      Enter PDB: targetPDB

      Example SQL Script:

      Note:

      Lines in bold are applicable only if your target database is a PDB. This SQL assumes that all the objects are created using the RCU prefix. If you have created objects without the prefix (for example tablespaces/users for JMS or TLogs, add these manually).

      $ cat << EOF > extract_ddl.sql
      set pages 0
      set feedback off
      set heading off
      set long 5000
      set longchunksize 5000
      set lines 200
      set verify off
      exec dbms_metadata.set_transform_param (dbms_metadata.session_transform, 'SQLTERMINATOR', true);
      exec dbms_metadata.set_transform_param (dbms_metadata.session_transform, 'PRETTY', true);
      accept PREFIX char prompt 'Enter RCU Prefix:'
      accept PDBNAME char prompt 'Enter PDB:'
      
      spool ddl.sql
      
      select 'alter session set container=&&PDBNAME;'
      from dual
      /
      SELECT DBMS_METADATA.GET_DDL('TABLESPACE',Tablespace_name)
      from  dba_tablespaces
      where tablespace_name like '&&PREFIX%'
      /
      set lines 600
      SELECT DBMS_METADATA.GET_DDL('USER',USERNAME)
      from DBA_USERS
      where USERNAME like '&&PREFIX%'
      /
      set lines 200
      SELECT DBMS_METADATA.GET_GRANTED_DDL ('SYSTEM_GRANT',USERNAME)
      from DBA_USERS
      where USERNAME like '&&PREFIX%'
      and USERNAME NOT LIKE '%_IAU_APPEND'
      and USERNAME NOT LIKE '%_IAU_VIEWER'
      /
      
      SELECT DBMS_METADATA.GET_GRANTED_DDL ('OBJECT_GRANT',USERNAME)
      from DBA_USERS
      where USERNAME like '&&PREFIX%'
      and USERNAME NOT LIKE '%TLOGS'
      and USERNAME NOT LIKE '%JMS'
      /
      
      spool off
      EOF

   2. Delete any object grants for system QT*_BUFFER views in the output ddl.sql.The buffer views will not exist in the target database and cause errors.

      $ sed -i.bak -e '/QT.*_BUFFER/d' /u01/installers/database/ddl.sql

8. Re-start the SOA DBMS queues. Connect as the SOAINFRA schema user and restart each queue that was stopped earlier.

   $ sqlplus <PREFIX>_SOAINFRA@sourceDB
   SQL> BEGIN
   
   DBMS_AQADM.START_QUEUE ('B2B_BAM_QUEUE');
   
   DBMS_AQADM.START_QUEUE ('EDN_OAOO_QUEUE');
   
   DBMS_AQADM.START_QUEUE ('EDN_EVENT_QUEUE');
   
   DBMS_AQADM.START_QUEUE ('IP_IN_QUEUE');
   
   DBMS_AQADM.START_QUEUE ('IP_OUT_QUEUE');
   
   DBMS_AQADM.START_QUEUE ('TASK_NOTIFICATION_Q');
   
   END;
   
   /
   SQL> COLUMN name FORMAT A32
   SQL> SELECT name,enqueue_enabled,dequeue_enabled  
   FROM USER_QUEUES where queue_type = 'NORMAL_QUEUE' order by name;
   
   NAME                             ENQUEUE DEQUEUE
   -------------------------------- ------- -------
   B2B_BAM_QUEUE                     YES        YES
   EDN_EVENT_QUEUE                   YES        YES
   EDN_OAOO_QUEUE                    YES        YES
   IP_IN_QUEUE                       YES        YES
   IP_OUT_QUEUE                      YES        YES
   TASK_NOTIFICATION_Q               YES        YES
   
   6 rows selected.
   SQL> exit

9. Re-start the WebLogic Server Managed Servers or clusters for OIM, SOA, and BIP.
10. Replicate the DDL SQL and the datapump dump files to the target database host.
    • oim.dmp
    • oim_system.dmp
    • ddl.sql

Clone the database from the source environment to the target environment by using RMAN. See Transferring Data with RMAN.

You can manually create a physical standby database using Data Guard. See Creating a Physical Standby Database in Oracle Data Guard Concepts and Administration.

After successfully restoring the backup to the target environment instances, do the following to start the domain:

• Start the Node Manager for the ASERVER_HOME.
• Start the Node Manager for the MSERVER_HOME on all nodes.

  Note:

  If you have a single DOMAIN_HOME, start the Node Manager associated with that DOMAIN_HOME.
• Start the Administration Server and check logs.
• Start the SOA Managed Server/Cluster and check logs.
• Start the Business Intelligence Platform Managed Server/Cluster and check logs.
• Start the OIM Managed Server/Cluster and check logs.

1. Log in to https://igdadmin.example.com/sysadmin and authenticate as xelsysadm.
2. In the left-pane, under System Configuration, click Scheduler. A popup window will appear.
3. In the Identity System Administration popup window, search for the scheduled job: LDAP Consolidated Full Reconciliation.
4. Click the LDAP Consolidated Full Reconciliation entry in the search results to view the job details.
5. Click Run Now to execute the job and verify the confirmation message: Job is running.
6. Periodically click the Refresh button and verify the job status.
7. When the Job Status shows Stopped, validate the Execution Status for Success. Check logs and troubleshoot as needed.
8. Click the Event Management tab and execute an empty search for all recent reconciliation events.
9. Spot-check the events to assure that the current status is either Creation Succeeded or Update Succeeded.