Testing Dbvisit Standby<--

To ensure Dbvisit Standby has been correctly configured on your environment and to ensure Dbvisit Standby will continue to keep the standby database up to date in all circumstances we recommend the following tests be performed.
These tests can be performed manually on the command line.
(In this example, the database is called ora10g)

Error rendering macro 'viewxls' : Failed to find attachment with Name Workbook18.xlsx

Dbvisit Standby Test – primary server	Example and explanation
dbvisit <DDC>	Example: dbvisit ora10g Normal Dbvisit Standby processing. It is a good idea to run this command several times in succession so that several log files are transferred to the standby server.
dbvisit -r <sequence_number> <DDC>	Example: dbvisit -r 23 ora10g Tests if a log file can be resent from a particular sequence. Note that the log file must be available on the primary server.
dbvisit –R <DDC>	Example: dbvisit -R ora10g Tests the resynchronization with the standby database after the standby database has been rebuilt. Can also be used to ensure the standby database has all the necessary log files after there has been an outage. The standby database must be up and running and the required log files must be available on the primary server.
dbvisit –i <DDC>	Example: dbvisit -i ora10g Reports on the archive log gap and transfer log gap between the primary database and the standby database. Dbvisit Standby will start the standby database if the standby database is not running and AUTO_START_STANDBY_DB = Yes
Edit dbv.env and change: IGNORE_ARCH_HIST=Y then run: dbvisit <DDC>	Example: dbvisit ora10g Edit the DDC file and update the IGNORE_ARCH_HIST variable and set this to Y. This forces Dbvisit Standby to use its own internal mechanism to find the next log file to transfer to the standby database. This test is useful, as the archive log file to transfer to the standby database is not always easily available in Oracle, especially if there has been a network outage and the standby database has not been updated for a while.
dbv_oraStartStop stop <DDC>	Example: dbv_oraStartStop stop ora10g Tests stopping the primary database.
dbv_oraStartStop start <DDC>	Example: dbv_oraStartStop start ora10g Tests starting the primary database.
dbv_oraStartStop status <DDC>	Example: dbv_oraStartStop status ora10g Tests obtaining the status of the database.
dbv_oraStartStop switchover <DDC>	Example: dbv_oraStartStop switchover ora10g Tests the Graceful Switchover and will transition the primary database to a standby database. This command must also be initiated on the standby server.
Add a datafile or new tablespace to the primary database. then run: dbvisit <DDC>	Example: dbvisit ora10g Run Dbvisit Standby on the primary server and then Dbvisit Standby on the standby server. The new datafile should be created and added to the standby database.

Dbvisit Standby Test – standby server	Example and explanation
dbvisit <DDC>	Example: dbvisit ora10g Normal Dbvisit Standby processing. If there are more than one log file, then Dbvisit Standby should apply all log files at once. After all the log files have been applied, run Dbvisit Standby again for several times. Dbvisit Standby will indicate that there will not be any new log files to apply. Run Dbvisit Standby again, until the threshold has been reached (MAX_TIMES_TRIED) and Dbvisit Standby should send an alert. Then run Dbvisit Standby again on the primary server, and then again on the standby server. Dbvisit Standby should apply the next available log file.
dbv_oraStartStop stop <DDC>	Example: dbv_oraStartStop stop ora10g Tests stopping the standby database.
dbv_oraStartStop start <DDC>	Example: dbv_oraStartStop start ora10g Tests starting the standby database.
dbv_oraStartStop status <DDC>	Example: dbv_oraStartStop status ora10g Tests obtaining the status of the database.
dbv_oraStartStop switchover <DDC>	Example: dbv_oraStartStop switchover ora10g Tests the Graceful Switchover and will transition the standby database to a primary database. This command must also be initiated on the primary server.