Why Use dbv_oraStartStop to Stop/Start Primary and Standby


Problem Description

 The below article explains the use of dbv_oraStartStop command is and what it does internally. These commands are present in  Version 7.0

Can we still use sqlplus commands to stop/start Primary and Standby databases. 


The dbv_oraStartStop command (executable) is there more specifically to be used for two key operations: Activation and Graceful Switchover (GS). But we have also enabled the options to start, stop and restart of the primary or standby database.

When used to perform Oracle start/stop operations, it will perform a number of checks behind the scenes. It will then use the same commands as would be used via the command line to start/stop a database as well as to open a standby database for recovery or read only.

Running dbv_oraStartStop with -h displays the command options and a brief summary of what they do.

Here is a summary of key options available (note the help includes information about the dbvisit command as well:

$ ./dbv_oraStartStop -h
Dbvisit Standby
- Oracle Standby Database Technology.
- Automated managed Standby Databases.
- Automatic creation of Standby Databases.
- Oracle Disaster Recovery.
dbvisit <DDC>
dbvisit -R <DDC>
dbvisit -i <DDC>
dbvisit -c <DDC> [nocksum]
dbvisit -ReverseCopy <DDC>
dbvisit -lic <DDC>
dbvisit -lic <DDC> <LICENSE\_KEY>
dbvisit -?
dbv_oraStartStop start <DDC>
dbv_oraStartStop stop <DDC>
dbv_oraStartStop open <DDC>
dbv_oraStartStop status <DDC>
dbv_oraStartStop activate <DDC> [Yes]
dbv_oraStartStop switchover <DDC> [UNIQUE_KEY]
dbv_oraStartStop update_ddc_file <DDC>
dbv_oraStartStop -?

Above is just an extract, and in the later help sections, these commands are explained:

dbv_oraStartStop options <DDC>
    Perform actions on the primary and standby database.
    options: start|stop|status|open|activate|switchover|update_ddc_file
dbv_oraStartStop start <DDC>
    Start Oracle database. This will automatically detect a primary or standby database and will start the database accordingly.
dbv_oraStartStop stop <DDC>
    Stop Oracle database. This will automatically detect a primary or standby database and will stop the database accordingly.
dbv_oraStartStop open <DDC>
   Open a standby database in READ-ONLY mode.
   This mode can be used to run report queries against the standby database. In this mode archive logs from the primary database cannot be applied.
dbv_oraStartStop status <DDC>
   Obtain the status of the database. This will indicate if
        - database is a primary or standby database,
        - database is open or closed,
        - database is in read-only mode.
dbv_oraStartStop activate <DDC> [Yes] [nosync]
    Activate the standby database to become the new primary database. MUST be done with caution as the process is NOT reverseable.
    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 (batch mode).
    -    If the nosynch paramter 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.
dbv_oraStartStop switchover <DDC> [UNIQUE_KEY]
   Initiates graceful switchover which reverses the role between the primary and the standby database. The primary database becomes
the standby database and the standby database becomes the primary database. No data will be lost. This process will shutdown and restart both the primary and standby database. The control files of both the primary and standby database will be rebuilt. All historic information in the control file will be lost.
A unique key will be required to initiate the switchover. This is a unique number that has not been used before.
Example: 6678
Dbvisit Standby will warn if the key has been used before. If key is specified on the command line, then process can be run
as batch. Dbvisit Standby will provide full rollforward or rollback steps if process is interrupted and cannot complete.
dbv_oraStartStop update_ddc_file <DDC>
   Updates the Dbvisit Database Configuration (DDC) file and reverses the primary and standby variables so that
Dbvisit Standby processing can be reversed. This command is automatically run as the last step of
graceful switchover and activate processing.

Regarding the starting and stopping of the databases, you are welcome to start the databases as you normally would, or you can use this command to help you do the same. As mentioned, it uses the same commands you would normally use to start and stop a database. When executed on the standby server it will pickup via the DDC file that it is a standby database and it will start it in the correct state: for recovery if the start option was specified, or read-only if the open option was specified.

Donna Zehl May 14, 2014 03:31

Have more questions? Submit a request