Align |
---|
When disaster strikes and the primary database is no longer available the standby database must be activated to become the new primary database to continue operation.
To activate and open the standby database for continued operation in the event of a disaster the following procedure must be used: |
On the standby server using CLI:
To Activate a standby database you have to make use of the "dbv_oraStartStop activate <DDC> [Yes] [nosync]" command (options in brackets [] are optional)
Command | Description |
---|---|
dbv_oraStartStop activate <DDC> [Yes] [nosync] | This command is used to Activate the standby database, during which process it becomes the new primary database. Important, this operation MUST be done with caution as the process is NOT reversable. This action is performed in the event that the primary database is no longer available. Dbvisit Standby will prompt before activating the standby database. If the Yes parameter is given then Dbvisit Standby will no longer prompt before activating the standby database (this option can be used in batch mode). If the nosync parameter is given, Dbvisit Standby will not transfer the updated (reversed) DDC file to the original primary if any schedules are running on the newly activated primary. When the standby database is activated it is no longer possible to keep the new primary and the old primary databases in sync. A new standby database must be created after activation. Updates the Dbvisit Database Configuration (DDC) file and reverses the primary and standby variables so that Dbvisit Standby processing can be reversed when a new standby database has been created. |
1. Manually run Dbvisit Standby to ensure all log files have been applied.
...
1. Manually run Dbvisit Standby to ensure all log files have been applied.
Home > Run > Run Interactive > Standby Server tab > select Database from drop-down menu > select Default from Run Action drop-down menu > Run
2. Activate the standby database. A prompt will be displayed to ask for confirmation:
...