Introduction

Note
Creating a standby database is performed on the primary server (primary node). If you are using Oracle RAC: you only need to run the Create Standby Database (CSD) process from one of the primary nodes (1st node recommended). It is important that you have a DDC file already created on both primary nodes. (Each nodes must have it's own DDC)

...

Step 3: Pre-flight check (Pre-Requisite Checks)

2. Dbvisit will now evaluate and check pre requisites for Standby creation.

During this phase a small instance will be started/stopped on the standby server to ensure some of the required pre-requisites are met.

If they are you will be directed to the next screen, if any of the checks fail an appropriate message will be shown.

The next step is to configure the Standby database parameters accordingly.

Recommendations:

Do not use the Direct Copy option unless the database is really small. Selecting "No" for this value is recommended for all environments.
File Compression during network transfer (File Compression) is not required as compressed backups is used, we recommend you leave this parameter at "No" to reduce extra overhead.

3. Once, All pre requisites checked now configure the Standby database parameters accordingly.

Image Removed

Image Added

If the primary database size is substantial and if even a compressed RMAN backup being transferred via the network is not feasible, we recommend you make use of the transportable media option. If using this option you have to make use of external attached storage such as a USB drive or something similar to which you can then create the backup and then transfer (example - courier it) to the standby site where it is attached to the standby server and the CSD process restarted from where it will continue where it left off.

The TMP location on the primary will be the location where Dbvisit Standby will create a local RMAN compressed backup of the Primary Database. Please make sure there is sufficient space in this location to keep a full compressed backup of the primary database.
The TMP location on the standby server will be the location to which the backup created on the primary will be transferred. From this location Dbvisit Standby will start the restore/creation of the standby database. Ensure there is sufficient space in this location to hold a full compressed backup of the primary database.

Image Added

If you want to update some of the Standby Database parameters, you should do it in the above section.
If the primary database is using ASM and the standby is using filesystem, you must modify some of the parameters in the above section such as db_recvoery_file_dest might be +FRA on ASM, but a filesystem location on the standby.
Keep in ming the memory parameters as they might need adjustment as well if your standby server has less memory than the primary server.

Image Added

The last step is to specify if this configuration should be saved as a template. This can be useful in environments where the standby database is recreated on a regular basis.
Note that if you do update the database structure (primary) on a regular basis, you will have to recreate the template (redo the CSD process) as the template that was saved might not contain all the required new changes.

Note

Before starting the Create Standby Database, verify the all parameters.

Click on Save Template option, sp that settings can be saved for future use.

...

Once the standby database creation process starts, the output of the different steps will be shown in the browser window.

Note
This process can take a very long time depending on the size of the database and the network

A detailed summary screen will show the progress of the standby database creation.

Image RemovedImage Added

...

Once the process is complete, a green light is shown.