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.

If the database already exists, make sure that the existing temp.dbf file is removed before performing a restore operation.
- 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.

Add the option UR=A in the CONNECT_DATA part of your tnsnames.ora entry to connect to your auxiliary database. The syntax should be as follows:
DUPDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = powerpc02)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = dupdb) (UR=A)
)
)

Ensure that the duplicate database connect string should be the same as duplicate database name if the duplicate database is not configured from CommCell console.

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. Make sure to use the password change_on_install when you create the password file for auxiliary database. 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.
When using a different host without configuring an instance, the SBT_LIBRARY uses the install path in the source client and not the destination client. Hence, in this case, the install path in the source and destination clients must be the same. It is recommended that you perform such restores using third party command line operations. However, if using the CommCell Console, set the sNOSBTLIBNAME registry key to Y on the CommServe. Also, ensure to run the Ora_install.sh on the auxiliary client.
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.
You may use reserved words as tablespace name for duplicate databases. However, if you select some tablespaces as SKIPPED tablespaces for duplicate databases, then you cannot choose those tablespaces that use the reserved words as tablespace names such as TEST. The duplicate restore will fail with the following error:

-------------------

Sample RMAN Script:

-------------------

connect catalog rman9i/password@XXXX

connect target sys/password@XXXX

connect auxiliary sys/password

run {

# Allocate the channel for the duplicate work

Allocate auxiliary channel ch1 type disk;

# set the new file names and locations for all datafiles

#

SET NEWNAME FOR DATAFILE 1 to 'C:\U01\ORADATA\DUP\SYSTEM01.DBF';

SET NEWNAME FOR DATAFILE 2 to 'C:\U01\ORADATA\DUP\UNDOTBS01.DBF';

...

...

SET NEWNAME FOR DATAFILE 11 to 'C:\U01\ORADATA\DUP\OEM_REPOSITORY.DBF';

SET NEWNAME FOR DATAFILE 12 to 'C:\U01\ORADATA\DUP\TEST01.DBF';

#

# Duplicate the database to DUP

#

DUPLICATE TARGET DATABASE TO DUP

LOGFILE

    GROUP 1 ('C:\U01\ORADATA\DUP\REDO01.LOG') SIZE 1000K,

    GROUP 2 ('C:\U01\ORADATA\DUP\REDO02.LOG') SIZE 1000K,

    GROUP 3 ('C:\U01\ORADATA\DUP\REDO03.LOG') SIZE 1000K

SKIP TABLESPACE 'TEST' ;

}

------------

Error Stack:

------------

.....

   set newname for datafile 11 to

"C:\U01\ORADATA\DUP\OEM_REPOSITORY.DBF";

   restore

   clone database

   skip tablespace TEST   ;

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-00601: fatal error in recovery manager

RMAN-03012: fatal error during compilation of command

RMAN-03028: fatal error code for command Duplicate Db : 600

RMAN-00600: internal error, arguments [8049] [] [] [] []

RMAN-01005: syntax error: found "test":

            expecting one of: "double-quoted-string, identifier,

                               single-quoted-string"

RMAN-01007: at line 27 column 21 file: Memory Script

This is because TEST is an Oracle reserved word, so it fails with RMAN-600 [8049] while compiling the memory script. Do not use reserved words for tablespace name. Please refer V$RESERVED_WORDS to get a list of Oracle Server reserved words.