Creating The Standby Database

Owned by KrupeshD (Unlicensed)
Last updated: Feb 08, 2015 by Anton Els (Unlicensed)
2 min read

Perquisites for creating the standby database are:

  1. Oracle software must be installed on the standby server.
  2. Enough free space on the standby server must be available for the standby database.
  3. The Oracle background (cdump, udump, bdump etc ) and admin directories are created. These directories can be created by Dbvisit if you choose the option to create missing filesystem directories automatically.

Dbvisit Standby allows the following options for creating the standby database:

a) Regular file system standby database with

      i) Same structure as primary database or
      ii) Different structure as primary database.

b) ASM standby database (for Oracle version 10.2 and higher) with

      i) Same structure as primary database or
      ii) Different structure as primary database.

If the new standby database has FRA enabled, please remove all files from FRA/<unique_db_name> folder on the standby server, prior to creating the database. This is to avoid resetting the standby database incarnation triggered by the presence of old database files in FRA.

 

RMAN Backups used during Create Standby Database (CSD)

The CSD process is by default making use of RMAN if the direct transfer is not used (using the direct transfer is not recommended unless the database is small).  To be more specific COMPRESSED BACKUPSET is used for the backups.  In certain scenarios it might be required to adjust the backup option to not use compressed backups or to rather use image copies.  This can be done by setting the RMAN_DBF_BACKUP_TYPE parameter in the primary server DDC file.  This parameter can be set to specify if a backupset, compressed backupset or image copies are to be used during the CSD operation:

 

Valid Options for the RMAN_DBF_BACKUP_TYPE  parameter are:

RMAN_DBF_BACKUP_TYPE=AS BACKUPSET
RMAN_DBF_BACKUP_TYPE=AS COMPRESSED BACKUPSET
RMAN_DBF_BACKUP_TYPE=AS COPY