Prerequisite Setup Steps for Creating a Duplicate Database

The following procedure describes the prerequisite setup steps for creating a duplicate database:

Before You Begin:

• Review information on the Duplicate Database feature before beginning this procedure.

Prerequisite setup steps:

• Run a full backup (along with the log files) on the original database.
• Create a duplicate Oracle database instance. If using a different host, create the duplicate database instance on the destination host.
  • Copy the init<SID>.ora file from the original database to the duplicate database instance.
  • Update the database name and the database file locations in the init<SID>.ora file for the duplicate database instance. Also, add the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters in the init<SID>.ora file. The DB_FILE_NAME_CONVERT parameter is used to redirect the data files and temp files to a target location. Similarly, the LOG_FILE_NAME_CONVERT parameter can be used to redirect the archive log files to a target location. The syntax is as follows:

    On Unix:

    DB_FILE_NAME_CONVERT=(source_of_df_path/,dup_of_df_path/,source_of_temp_path/,dup_of_temp_path/,...)

    LOG_FILE_NAME_CONVERT=(source_of_log_path/redo,dup_of_log_path/redo)

    On Windows:

    DB_FILE_NAME_CONVERT=('sourcE_of_df_path/','dup_of_df_path/','source_of_temp_path/','dup_of_temp_path/',...)

    LOG_FILE_NAME_CONVERT=('source_of_log_path/redo','dup_of_log_path/redo')

    When using these parameters on a Windows computer, the file paths should be entered in uppercase.

    Make that all the other parameters in the init<SID>.ora file is same as that in the original database.

• In the case of table restore, provide the log_archive_dest_1 parameter in the init<auxiliary_sid>.ora file for the specified auxiliary instance.
• Create new Oracle Services if using a Windows computer.
• If using the same host, add the duplicate database instance name in the Listener.ora and Tnsnames.ora files.
• If using a different host, add the duplicate database instance name in the Listener.ora file on the destination host and Tnsnames.ora files on the destination and source hosts. Also, add the original database name in the Tnsnames.ora file on the destination host.
• Restart the Listener.
• Provide a valid connect string for the auxiliary channel (used to duplicate the database). The system assumes and uses sys/change_on_install for the auxiliary channel. If using a different host, make sure that a valid connect string (sys/sys@<SID name>) is provided in the Instance Properties (Details) tab instead of a '/'.
• Startup the duplicate database instance in the NOMOUNT mode.
• If using a different host, ensure that the Oracle iDataAgent is installed on the Destination host.
• If required, you can create a new Oracle instance for the duplicate database in the CommCell Console, open the instance properties and verify that the Oracle instance status of the duplicate database is STARTED.