/
Graceful Switchover (role reversal)

Graceful Switchover (role reversal)

Nov 07, 2012

Dbvisit Standby Graceful Switchover limitations

In some cases, on Windows the registry setting ORA_DB _{}AUTOSTART needs to be set to FALSE. (where DB is the name of your database) The setting is in: HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE. (Only set this if graceful switchover is not successful initially).

If the database uses ASM, then the ASM instance must be at least Oracle version 11.1. This limitation is only for the ASM instance and not for the database itself.

How the Dbvisit Standby Graceful Switchover process works

  1. Dbvisit Standby checkpoints are used to ensure the process between the primary and standby database are synchronised.

  2. Users should be disconnected from the main primary database.

  3. Dbvisit Standby Graceful Switchover is initiated with a simple command on the primary server and the standby server.

  4. Main primary database is shutdown during transition.

  5. Standby database is shutdown during transition.

  6. Main primary database transitions to standby database on primary server in matter of minutes*.

  7. Standby database transitions to primary database on standby server in matter of minutes*.

  8. Users can re-connect to primary database on standby server and continue working, with no data loss.

  9. Maintenance can proceed on primary server.

  10. Optionally Dbvisit Standby can keep the standby database on the primary server up to date during the scheduled maintenance outage.

  11. At the end of the scheduled maintenance the databases are transitioned back to their original state in matter of minutes*.

*Depending on speed of network and distance between primary and standby server.