Graceful Switchover errors and recovery

When an error occurs during Graceful Switchover on either the primary or the standby server, processing will stop on both the primary and standby servers. 
There are two options when an error occurs depending on where (which checkpoint) the error occurred. The options are:

1. Rollback. Switchover processing was not completed far enough to transition the databases to their new roles. The databases will remain in their original state. Manual steps may be required to complete the rollback. These steps will be shown in the Dbvisit Standby error notification. These steps are also shown below in the Graceful Switchover rollback or roll forward action section.

2. Roll forward. Switchover processing was completed far enough to transition the databases to their new roles. The primary databases will become the standby database, and the standby database will become the new primary database. Manual steps may be required to complete the transition. These steps will be shown in the Dbvisit Standby error notification. These steps are also shown below in the Graceful Switchover rollback or roll forward action section.

Backup copies of the redo logs, controlfiles or database configuration file may be needed for rollback purposes. The backup copies are held in the same location as the original file. The name of the backup copy will be displayed during Graceful Switchover processing and will be present in the Graceful Switchover log file. See "Graceful Switchover log files" at the end of this section for the location of the log files.
The Dbvisit Database Configuration file (dbv_DDC.env) is automatically updated as part of normal Graceful Switchover processing. All variables associated with the transition from the primary database to the standby database will be updated automatically to allow Dbvisit Standby to continue processing after Graceful Switchover. If Graceful Switchover has not completed successfully and the database configuration file has not been updated, the following command may be used to update the database configuration file automatically: