Performing Oracle Advanced Recovery - OCP: Oracle Database 12c Administrator Certified Professional - page 290

You will need to decide where you want to put the database files that will be associated
with the newly duplicated database. Files like the control files, the online redo logs, and
the database data files need a home, and you have to know where that will be before you
start the duplication process. In the next step, you will use this information to configure
the auxiliary instance for duplication.
Before you can begin the duplication process, you must configure the auxiliary instance
so that it will start. To do so, follow these steps:
1. Configure any OS-specific requirements.
Different operating systems require that certain prerequisites be completed before you
can start a database instance. For example, in Windows you must create the Windows
service, and in most Unix flavors you will need to configure shared memory. You will
need to make sure that these preconfiguration steps are complete before you can start
the auxiliary instance and begin the duplication process.
2. Configure the database password file for the auxiliary instance.
The auxiliary instance will require a password file. Use the ORAPWD command (see
Chapter 3 for more on ORAPWD ) to create the password file. If you prefer, you can instruct
Oracle to copy the password file from the target database to the duplicated database when
you issue the DUPLICATE command.
3. Configure Oracle networking for the auxiliary instance.
If you will be executing the DUPLICATE command from a host other than the destination
host, or if you are going to use active database duplication, you will have to configure
Oracle networking so that you can connect to the auxiliary instance via Oracle Net. You
can use the Oracle Net Configuration Assistant to configure both the database listener
and the tnsnames.ora file for naming resolution.
4. Configure the database parameter file for the auxiliary instance.
Configuring the database parameter file correctly can ensure successful database
duplication. Incorrectly configuring the parameter file can be a frustrating exercise
in futility. The parameter file must be configured to be able to start the auxiliary
instance. The parameters listed in Table 7.2 are available for use during the database-
duplication process. You may not need to use all of the parameters listed in Table 7.2
when duplicating databases. In some cases these parameters can also be defined on
the RMAN command line as parameters of the DUPLICATE command.

TABle 7.2 Auxiliary database parameters related to database duplication

Parameter Name Purpose

DB_NAME The name of the duplicated database. This same name will be

used in the RMAN DUPLICATE command. This name should
be unique for databases on a given host. This parameter is a
required parameter for any database duplication.