Step 6 - Dbvisit Standby configuration Complete

Owned by KrupeshD (Deactivated)
Last updated: Feb 16, 2012Version comment
2 min read

The Dbvisit Standby setup and configuration is now complete. Through the automatic scheduling, Dbvisit Standby will keep the standby database up to date. 
The DDC file can be edited with any ascii editor to change a setting or threshold. The DDC file should be edited on the primary server only.

Further recommendations

1. Schedule the Dbvisit Standby Log gap report every hour on the primary serverto report on the gap between the primary and the standby database. This report can be scheduled through cron or through the Dbvserver build in scheduler. To alert if the standby database falls to far behind, set ARCHIVE_LOG_GAP_THRESHOLD and TRANSFER_LOG_GAP_THRESHOLD.

a. Scheduling through Dbvserver:

b. Scheduling through Task Scheduler: 

Specify "-i" as first parameter and database name as the second parameter to the Dbvisit Standby executable. 

2. Open the standby database in READ ONLY mode to periodically to test if the standby database is up to date.

a. Open the standby database in READ ONLY mode through the GUI.

Choose Run -> Run Interactive -> Standby Server tab.

b. Open the standby database in READ ONLY mode through the CLI 

 

C:\Program Files\Dbvisit>dbv_oraStartStop open w120n

While the standby database is in READ ONLY mode, it is not possible to apply the latest changes.

The standby database must be restarted to apply the latest changes. To restart the standby database

c. To restart the standby database in GUI

 

d. To restart the standby database in CLI

 

C:\Program Files\Dbvisit>dbv_oraStartStop restart w120n

3. Once Dbvisit Standby has been tested and configured, change SUCCESSMAIL=Y to SUCCESSMAIL=N. This will ensure only exception alerts are sent.


Please go to www.dbvisit.com for full documentation, forums, blogs and logging support issues.