Create a Standby Database on a Different Host without the Instance Configured

The following procedure describes the steps involved in creating a standby database on a different host without the instance configured.

Before You Begin

Review the general restore requirements accessed from Restore Backup Data, and the agent-specific restore requirements accessed from Advanced Restore - Oracle iDataAgent prior to performing any restore.
Review information on the Duplicate Database feature before beginning this procedure.
Prerequisite Setup Steps:
- Run an online full backup with current control file. See Backup Control File for StandBy for more information. This backup will be used to create the standby database and standby control file.
- Standby Database Preparation (We strongly recommend that you consult the Oracle Data Guard Concepts and Administration guide for more detailed information on this process):
  - Set the following initialization parameters in the primary initialization parameter file init<standbydb>.ora (i.e., Startup PFile) on source (primary) host.
    LOG_ARCHIVE_DEST_1='LOCATION=C:\Oracle\Oradata\TSH1\Archive MANDATORY REOPEN=30'
    
    LOG_ARCHIVE_DEST_2='SERVICE=stby1 LGWR SYNC AFFIRM'
  - Create an initialization parameter file, init<standbydb>.ora for the standby database and set the following initialization parameters on Standby host:
     *.log_archive_dest_1='LOCATION=/ LOCATION_OF_DESTINATION_DB_ARCHIVELOG /arch'
  
     *.STANDBY_ARCHIVE_DEST='/ LOCATION_OF_STANDBY_DB_ARCHIVELOG /stdbyarch'
  
     *.STANDBY_FILE_MANAGEMENT=auto
  
       DB_FILE_NAME_CONVERT=('/DATA_FILE_PATH_ON_SOURCE_MACHINE/stdby', '/ORACLE_DATA_FILE_PATH_ON_STANDBY_MACHINE/stdby/')
  
      LOG_FILE_NAME_CONVERT=('/ DATA_FILE_PATH_ON_SOURCE_MACHINE /stdby', '/ ORACLE_DATA_FILE_PATH_ON_STANDBY_MACHINE /stdby/')
  - Perform any Oracle Net setup and configuration required to connect to the standby database.
    For example, set up the listener and configure the destination computer's $TNS_ADMIN/tnsnames.ora file for the standby database.
    
    On Source computer:
    
    <Standbydb1_use_diff_connection_string> =
    
    (DESCRIPTION =
    
    (ADDRESS = (PROTOCOL = TCP)(HOST = destination_host_name)(PORT = 1521))
    
    (CONNECT_DATA =
    
    (SERVER = DEDICATED)
    
    (SERVICE_NAME = <standbydb_use_same_db_name_as_primary>)
    
    (UR = A)
    
    )
    
    )
    
    <Standbydb_primary> =
    
    (DESCRIPTION =
    
    (ADDRESS = (PROTOCOL = TCP)(HOST = primary_host_name)(PORT = 1521))
    
    (CONNECT_DATA =
    
    (SERVER = DEDICATED)
    
    (SERVICE_NAME = <standbydb_same_as_destination><)
    
    )
    
    )
    
    On standby computer:
    
    <standbydb1_destination_connection_string> =
    
    (DESCRIPTION =
    
    (ADDRESS = (PROTOCOL = TCP)(HOST = destination_standby_host_name)(PORT = 1521))
    
    (CONNECT_DATA =
    
    (SERVER = DEDICATED)
    
    (SERVICE_NAME = <standbydb_destination_db_name_same_as_primary>)
    
    (UR = A)
    
    )
    
    )
    
    <standbydb_primary_connection> =
    
    (DESCRIPTION =
    
    (ADDRESS = (PROTOCOL = TCP)(HOST = primary_host_name)(PORT = 1521))
    
    (CONNECT_DATA =
    
    (SERVER = DEDICATED)
    
    (SERVICE_NAME = <standbydb_primary_db>)
    
    )
    
    )
- The system assumes to use sys/change_on_install for the auxiliary channel while creating password file for standby database on destination host. However, you must use this connect string to connect to the auxiliary database when the instance is not configured. Once the instance is configured, ensure that you set the same password for the SYS user account for every primary and standby databases, for the redo data transmission to succeed.
- Start the standby database in NOMOUNT mode.
- Do not create a new instance for the destination host in the CommCell Console.
- 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.
- When using a different host without configuring an instance, it is recommended to create the standby database from third party command line as follows:
  run {
  
  allocate auxiliary channel ch1 type 'sbt_tape'
  
  PARMS="SBT_LIBRARY=<destination_software_install_path>/Base/libobk.so,BLKSIZE=262144,ENV=(CvInstanceName=<destination_instance_name>,CvClientName=<destination_host_name>,CvOraSID=<destination_oracle_sid>)"
  
  TRACE 0;
  
  set until scn ##### ;
  
  duplicate target database for standby
  
  dorecover
  
  ;}
- Ensure that the Oracle iDataAgent is installed on the Destination host.

For Oracle 10g or higher, ensure that you set the Standby Role Initialization parameter, DB_FILE_NAME_CONVERT,to add all the temp data files from the primary database location to the standby database location, as follows:

DB_FILE_NAME_CONVERT='<primary_database_temp_datafile_old _location>','<standby_database_temp_datafile_new_location>'

If this parameter is not set, restore will fail with the following error message:

temporary file TEMP01.DBF conflicts with file used by target database

Required Capability: See Capabilities and Permitted Actions

To create a standby database on a different host without the instance configured:

From the CommCell Console, right-click the source host instance then select All Tasks -> Restore.
From the Oracle Restore Options (General) dialog box, select the Duplicate DB checkbox and enter the Catalog Connect string, then click Advanced.
Click the Duplicate DB Options tab, select the Duplicate For Standby option then enter the Oracle System Identifier for the standby database in the Oracle SID field. Optionally, you may configure any of the following options as desired:
- Time Zone - Select a time zone for a point-in-time recovery.
- No Filename Check - Select this option to prevent RMAN from performing a check for target datafiles sharing the same names as the duplicated files to see if they are in use. This option is required when you are using the same path (i.e., the standby and primary datafiles and logs have identical filenames).
- Do Recover - Select this option to recover the standby database after it has been created.
Click the Recover tab, then select the appropriate recover option.
Click the Redirect tab, then choose one of the following and click OK:
- To redirect all tablespaces to the same location, select the Redirect All Table Spaces to: checkbox then type in or Browse to the new path.
- To redirect tablespaces/datafiles to different locations, select the Redirect checkbox then click the desired objects in the Object column to highlight them, and either type in or Browse to the new path. Click Apply. Repeat this process until all tablespaces/datafiles have been redirected.
Select any other applicable options in the Oracle Duplicate Options dialog box, then click OK.
From the Oracle Restore Options (General) dialog box, select the Destination Client from the list (when the instance is not configured, the destination client must be the source host).
Begin or schedule the restore. Once you entered the standby database name and selected the destination computer name, take a look at the database state and ensure that the standby database is in NOMOUNT mode then click Yes to continue.
Verify that the restore completed successfully and that the database is restored to the destination host. If you selected the Recover option verify that the database is consistent.
Once the job is completed, the new database will be on MOUNT mode for the standby database. If the user require to enable log shipping, execute the following sql command:
Alter database recover managed standby database disconnect;