D
Creating a Physical St andby Database with Recovery Manager

D.3 Setting Up the Standby Instance

No matter which standby creation scenario you choose, you must first start the stand by instance and then connect RMAN to this instance. The details of this procedure vary depending on whether or not the standby and pr imary sites have a different directory structure.

To start the standby instance:

1. Use an operating system util ity to copy the SPFILE (or the initialization parameter file) from the target host to the standby host. Set all required parameters i n the standby database initialization parameter file as described in Section 3.2.3. For exampl e, if creating the standby database on a separate host with a different directory structure, edit:
   • Initialization parameters that end with _DEST and _PATH and specify a path name
   • DB_FILE_NAME_CONVERT so that it captures all the target datafiles and converts them appropriately, for example, from tbs_* to sbytbs_*
   • LOG_FILE_NAME_CONVERT so that it captures all the redo log files and converts them appropriately, for example, log_* to sbylog_*
   < /a>

   For example, the following are sample parameter settings in the standby database initialization parameter file:

   STANDBY_ARCHIVE_DEST = /fs3/arc_dest/
   LOG_ARCHIVE_FORMAT = log%d_%t_%s_
   %r.arc
   DB_FILE_NAME_CONVERT = '/oracle', '/fs3/oracle', '/dbf', '/fs3/oracle'
   LOG_FILE_NAME
   _CONVERT = '/oracle', '/fs3/oracle'
   
   

2. Use SQ L*Plus to start the standby instance without mounting it. For example, enter the following to connect to sbdb1 as SYS (who has SYSDBA privileges) and start the database:

   SQL> CONNECT SY
   S/sys_pwd@sbdb1 AS SYSDBA
   SQL> STARTUP NOMOUNT PFILE=initSBDB1.ora
   
   

3. Use SQL*Plus to mount or open the primary database if it is not already mounted or o pen. For example, enter the following to connect to prod1 as SYS and open the database:

   <
   a name="636827">SQL> CONNECT SYS/sys_pwd@prod1 AS SYSDBA
   SQL> STARTUP PFILE=initPROD1.ora
   
   

   Ensure the recovery catalog database is open. For example, enter the following to connect to catdb as SYS and open the recovery catalog database:

   <
   /a>SQL> CONNECT SYS/oracle@catdb AS SYSDBA
   SQL> STARTUP PFILE=initCATDB.ora
   
   

   < /li>
4. The standby instance must be accessible through Oracle Net. Before proce eding, use SQL*Plus to ensure you can establish a connection to the standby instance. Note that you must connect to the standby insta nce with SYSDBA privileges, so a password file must exist.
5. Connect to the target database, the standby instance, and (if you use one) the recovery catalog database. Note that you specify the < em class="Italic">primary database with the TARGET keyword and the standby instance with th e AUXILIARY keyword.

   In the following example, connection is established wi thout a recovery catalog by using operating system authentication:

   % rman TARGET / AUXILIAR
   Y SYS/sys_pwd@sbdb1
   

D.4 Creating a Standby Database with the Same Directory Structure

1. Follow the steps in Section D.3 . Make sure to set all necessary parameters in the standby initialization parameter file.
2. Run the DUPLICATE command. Perform the following steps:
   1. If automatic channels are not configured, then manually allocate at least one auxiliary channel.
   2. Specify new filenames for the standby database datafiles with SET NEWNAME commands.
   3. Issue the DUPLICATE command.
   < a name="636964">

   The following example uses a configured channel to create the standby database:

   RUN
   {
     # set new filenames for the datafiles
     SET NEWNAME FOR DATAFILE 1 TO '?/dbs/standby_data_01.f'; 
     SET NEWNAME FOR DATAFILE 2 TO '?/dbs/standby_dat
   a_02.f'; 
     .
     .
     .
     # run the DUPLICATE comma
   nd
     DUPLICATE TARGET DATABASE FOR STANDBY;
   }
   

D.5.2.2 Creating the Standby Database and P erforming Recovery

To create the standby database and perform recover y, specify the DORECOVER option on the DUPLICATE command.

To use the SET NEWNAME command to name standby database files and perform recovery:

1. Follow the steps in Section D.3. Ma ke sure to set all necessary parameters in the standby initialization parameter file.
2. Run the DUPLICATE command. Follow these steps:
   1. Ensure the end recovery time is greater than or equal to the checkpoint SCN of the standby control file and t hat a log file containing the checkpoint SCN is available for recovery (as described in Section D. 2.2).
   2. If desired, issue a SET command to specify the end time, SC N, or log sequence number for incomplete recovery.
   3. If automatic channels are not c onfigured, then manually allocate at least one auxiliary channel.
   4. Specify new file names for the standby database datafiles.
   5. Issue the DUPLICATE command with the DORECOVER option.

   For example, enter the following at the RMAN prompt to use a configured channel to create the standby database:

   # If desired, issue a L
   IST command to determine the SCN of the standby 
   control file.
   # The SCN to which you recover must be greater th
   an or equal to the control 
   file SCN.
   
   LIST BACKUP OF CONTROLFILE;
   LIS
   T COPY OF CONTROLFILE;
   RUN
   {
     # If desired, issue a SET command to te
   rminate recovery at a specified 
   point.
     # SET UNTIL TIME 'SYSDATE-7';
   
   <
   /a>  # Set new filenames for the datafiles
     SET NEWNAME FOR DATAFILE 1 TO '?/dbs/standby_data_01.f'; 
     SET NEWNAME FOR DATAFILE 2 TO '?/dbs/standby_data_02.f'; 
     .
     .
     .
     DUPLICATE TARGET DATABASE FOR STANDBY
       DORECOVER;
   }
   
   
   

   RMAN uses all incremental backups, archived redo log file backups , and archived redo log files to perform incomplete recovery. The standby database is left mounted.

In this procedure, you use CONFIGURE AUXNAME commands to name the standby datafiles.

To create the standby database without performing recovery, do not specify the < code>DORECOVER option on the DUPLICATE command. By default, RMAN leaves the standby database mounted and does not recover it.

To use CONFIGURE AUXNAME to name standby database files wi thout performing recovery:

1. Follow the steps in Section D.3. Make sure to set all necessary parameters in the standby initialization parameter file.
2. Configure the auxiliary names for the datafiles. For exa mple, enter:

   # set auxiliary names for the datafiles     
   CONFIGURE AUXNA
   ME FOR DATAFILE 1 TO '/oracle/auxfiles/aux_1.f'; 
   CONFIGURE AUXNAME FOR DATAFILE 2 TO '/oracle/auxfiles/aux_2.f'
   ; 
   .
   .
   .
   CONFIGURE AUXNAME FOR DATAFILE n TO '/oracle/auxfiles/aux_n.f'; 
   
   

3. Run the DUPLICATE command. If automatic channels are not configured, manually allocate at least one auxiliary channel before issuing the DUPLICATE command, as in the following example:

   RUN
   {
     # allocate at least one auxiliary channel of type DISK or sbt 
     ALLOCATE AUXILIARY CHANNEL standby1 DEVICE TYPE sbt; 
     .
     .
     .
     # issue the DUPLICATE command
     DUPLICATE TARGET DATABASE FOR STANDBY;
   }
   
   

4. Unspecify the auxiliary names for the datafiles so that they are not overwritten by mistake. For example, enter the following at the RMAN prompt:

   # un-specify auxiliary names for the datafiles
   CONFIGURE AUXNAME FOR DATAFILE 1 CLE
   AR; 
   CONFIGURE AUXNAME FOR DATAFILE 2 CLEAR; 
   .
   .
   .
   CONFIGURE AUXNAME FOR DATAFILE n CLEAR; 
   

D.5.3.2 Creating the Standby Database and Performing Recovery

To create the standby database and perform recove ry, specify the DORECOVER option on the DUPLICATE command.

To use CONFIGURE AUXNAME to name standby files and perform recovery:

1. Follow the steps in Section D.3. Make sure to set all necessary parameters in the standby initialization parameter file.
2. Set the auxiliary names for the datafiles. For example, enter the following:

   # set auxiliary n
   ames for the datafiles     
   CONFIGURE AUXNAME FOR DATAFILE 1 TO '/oracle/auxfiles/aux_1.f'; 
   CONFIGURE AUXNAME FOR DATAFILE 2 TO '/oracle/auxfiles/aux_2.f'; 
   .
   .
   .
   CONFIGURE AUXNAME FOR DATAFILE n TO '/oracle/auxfiles/aux_n.f
   '; 
   
   

3. Run the DUPLICATE command . Follow these steps:
   • Ensure the end recovery time is greater than or equal to the checkpoint SCN of the standby control file and that a log file containing the checkpoint SCN is available for recove ry (as described in Section D.2.2).
   • If d esired, issue a SET command to specify the end time, SCN, or log sequence number for incomplete recovery.
   • If automatic channels are not configured, then manually allocate at least one auxiliary chann el.
   • Issue the DUPLICATE TARGET DATABASE for standby command.

   For example, enter the following at the RMAN prompt to use a con figured channel to create the standby database:

   # If desired, issue a LIST command to deter
   mine the SCN of the standby 
   control file.
   # The SCN to which you recover must be greater than or equal to the c
   ontrol 
   file SCN.
   LIST BACKUP OF CONTROLFILE;
   LIST COPY OF CONTROLFILE;
   
   DUPLICATE TARGET DATABASE FOR STANDBY
     DORECOVER;
   
   

   RMAN uses all incremental backups, archived redo log file backups, and archived redo log files to perfo rm incomplete recovery. The standby database is left mounted.

4. Clear the auxiliary name settings for the datafiles so that they are not overwritten by mistake. For example, enter the following at the RM AN prompt:

   # un-specify auxiliary names for the datafiles
   CONFIGURE AUXNA
   ME FOR DATAFILE 1 CLEAR; 
   CONFIGURE AUXNAME FOR DATAFILE 2 CLEAR; 
   .
   .
   
   .
   CONFIGURE AUXNAME FOR DATAFILE n CLEAR; 
   

D.6 Creating a Standb y Database on the Local Host

When creating a standby database on the same host as the primary database, follow the same procedure as for duplicating to a remote host with a different directory structure as described in Section D.5.

Note the following rest rictions when creating a standby database on the same host as the primary database:

• You can create the standby database in the same Oracle home as the target database, but you must convert the fil enames with the same methods used for conversion on a separate host. That is, you must treat a standby database in the same Oracle ho me as if it were a database on a separate host with a different directory structure. You must not use the sam e names for standby and primary database files when the two databases are on the same machine.
• You must set the DB_UNIQUE_NAME initialization parameter on both databases.

  CAUTION: Do not use the NOFILENAMECHECK option when creating the standby database in the same Oracle home as the prim ary database. If you do, then you may overwrite the target database files or cause the DUPLICATE command to fail with an error.

D.7 Creating a Standby Database with Image Copies

This section contains these topics:

• Overview
• When Copies and Datafiles Use the Same Names
• When Copies and Datafiles Use Different Names

D.7.1 Overview

The main restriction when using RMAN image copies to create the standby datafiles is that the image copy filenames for datafiles and archived redo log files o n the primary and standby hosts must be the same. For example, assume that datafile 1 is named /oracle/dbs/df1.f on the primary host. If you use the RMAN COPY command to copy this datafile to /data/df1.f, then this image copy m ust exist on the standby host with the same filename of /data/df1.f. Otherwise, RMAN cannot locate the metadata for the standby image copy in its repository.

You have two main ways of populating the standby host with the image copies:

• Transferring them manually with ft p or some other utility
• Mounting the standby directory structure on the primary host with a network file system (NFS)

When you use the NFS method, you can cre ate a directory on the primary host that maps to a directory on the standby host. If you use this method, then the NFS mount point on both machines must have the same directory name. For example, you can map /data on the primary host to /data on the standby host, but you cannot map /data on the primary host to /dir on the standby host (unless yo u use functionality such as symbolic links in UNIX or logical drives on Windows NT).

To create the standby database and perform recovery, specify the DORECOVER option on the < code>DUPLICATE command.

To create a standby database when the co pies and standby datafiles have different names and perform recovery:

1. Connect to the primary database, standby instance, and, if desired, the recovery catalog database. Fo r example, enter:

   % rman TARGET sys/sys_pwd@prod1 AUXILIARY sys/sys_pwd@sbdb1 CATALOG 
   rman/ca
   t@catdb
   
   

2. Mount but do not open the primary database and ensure the database was closed cleanly before mounting. For example, enter:

   START
   UP MOUNT PFILE=initPROD1.ora
   
   

3. Either set DB_FILE_NAME_CONVERT in the standby initialization parameter file so that standby datafile filenames are translated from t he primary datafile filenames, or issue SET NEWNAME commands. For example, set the DB_FILE_NAME_CONVE RT parameter as follows:

   DB_FILE_NAME_CONVERT = '/oracle/dbs', '/dsk2/oracle'
   
   
   

4. Run the DUPLICATE command. Follow these steps:
   1. Ensure the end reco very time is greater than or equal to the checkpoint SCN of the standby control file and that a log file containing the checkpoint SC N is available for recovery (as described in Section D.2.2).
   2. If desired, issue a SET command to specify the end time, SCN, or log sequence number for recovery.
   3. If automatic channels are not configured, then manually allocate at least one auxilia ry channel for the duplication.
   4. Copy every datafile and the standby control file.< /li>
   5. Archive the current online redo log files.
   6. Issue the DUPLICATE command with the DORECOVER option.

   For example, enter the following:

   COPY 
     DATAFILE 1 TO '/dsk2
   /oracle/df_1.f',
     DATAFILE 2 TO '/dsk2/oracle/df_2.f',
     DATAFILE 3 TO '/dsk2/oracle/df_3.
   f',
     DATAFILE 4 to '/dsk2/oracle/df_4.f',
     DATAFILE 5 TO '/dsk2/oracle/df_5.f',
     DATAFILE 6 TO '/dsk2/oracle/df_6.f',
     DATAFILE 7 TO '/dsk2/oracle/df_7.f',
   
    DATAFILE 8 to '/dsk2/oracle/df_8.f',
     DATAFILE 9 TO '/dsk2/oracle/df_9.f',
     DATAFILE 10
   TO '/dsk2/oracle/df_10.f',
     DATAFILE 11 TO '/dsk2/oracle/df_11.f',
     DATAFILE 12 to '/dsk2
   /oracle/df_12.f',
     CURRENT CONTROLFILE FOR STANDBY TO '/dsk2/oracle/cf.f';
     SQL 'ALTER SY
   STEM ARCHIVE LOG CURRENT'; 
     DUPLICATE TARGET DATABASE FOR STANDBY
       DORECOVER;
   
   

   RMAN uses all incremental backups, archived redo log file backups, and arc hived redo log files to perform incomplete recovery. The standby database is left mounted.

D.8 Usage Scenario