Running or executing Dbvisit Standby

Dbvisit Standby must be run and scheduled separately on the primary and the standby server, but the commands are the same. Dbvisit Standby will detect on which server it is running automatically. It is recommended that Dbvisit Standby is run manually in the foreground on both the primary and standby server for the first few times before it is scheduled to run automatically in the background.

Two ways to run Dbvisit Standby manually on all platforms

Dbvisit Standby can be run either from the traditional command line interface (CLI) or through a web-based interface (GUI).
The CLI commands will be indicated by 

The GUI commands wil be indicated by 

Executing Dbvisit Standby CLI commands - Windows

Dbvisit Standby commands are run from the Dbvisit Standby command console.
Start the Dbvisit Standby command console from the Start Menu > Programs > Dbvisit > Standby.

Executing Dbvisit Standby CLI commands - Linux/Unix

Go to the Dbvisit Standby install directory:

cd /usr/local/dbvisit/standby

Executing Dbvisit Standby GUI commands – (web-based)

The Dbvserver web server must be started to execute Dbvisit GUI or web-based commands. To access the web-based GUI interface, point the browser to the IP address of the server and specify default port 8081:

Running Dbvisit Standby on primary server

Dbvisit Standby can run as follows:

1. Execute Dbvisit Standby on the primary server:

 dbvisit <DDC>
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration

For example:

 Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Default from Run Action drop-down menu > Run

Note

1. The first time that Dbvisit Standby executes, the Dbvisit Standby installation and configuration files will be copied over to the standby server. This is equivalent to running Dbvisit Standby with the -c option, or Copy Software from the Run Action menu on the Run Interactive web-based interface screen.

2. The first time Dbvisit Standby executes, the standby database must be up and running because Dbvisit Standby has to determine which initial log is needed for the standby database. Subsequent times Dbvisit Standby executes on the primary server the standby database does not need to be up and available.

3. In the examples the Dbvisit Standby Archive log Management Module (AMM) is turned on. This can be turned off by setting ARCHSOURCE_MANAGEMENT=N for the primary server and ARCHDEST_MANAGEMENT=N for the primary server in the DDC file, or by updating this parameter directly via the following menu path in the web-based interface: Home > Setup > Update Dbvisit > Update Dbvisit Configuration.

Subsequent times that Dbvisit Standby executes, the Dbvisit Standby installation will not be copied over to the standby server and Dbvisit Standby will NOT contact the standby database. The standby database does not have to be available to transfer the archive log files to the standby database.

For example:

 For example:

Running Dbvisit Standby on the standby server

2. Execute Dbvisit Standby on the standby server:

dbvisit <DDC>
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration.

For example:

Home > Run > Run Interactive > Standby Server tab > select Database from drop-down menu > select Default from Run Action drop-down menu > Run

If there are no logs to be applied then Dbvisit Standby will indicate this.

For example:

 

For example:

To delay the application of the logs to the standby database, the setting APPLY_DELAY_LAG_MINUTES can be used. This creates a lag time in minutes between the archiving of a redo log at the primary database and the application of the log on the standby database. The archive logs are still transferred to the standby server as normal without delay.To turn off APPLY_DELAY_LAG_MINUTES, set to 0. See Dbvisit Standby configuration variables (DDC) for more details.

3. Manually copy the Dbvisit Standby installation to the standby server. This option can only be given on the primary server.

dbvisit -c <DDC> [nocksum]
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration. nocksum is optional and if specified no checksum comparison will be done between the original file or program and the transferred file or program.
For example:

Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Copy Software from Run Action drop-down menu > Run

 

If configuration changes are made to the database Configuration file (DDC), Dbvisit Standby will automatically detect this and update the standby server (next time Dbvisit Standby executes on the primary server), if setting SYNCH_DBVISIT_INSTALL=Y. This is the default setting.

4. Manually copy the Dbvisit Standby installation from the standby server to the primary server. This option is only possible through the command line, as this functionality is not included in the web-based interface.

dbvisit -ReverseCopy <DDC>
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration.

This option can be used if configuration changes have been made on the standby server and these should be copied to the primary server. The whole Dbvisit Standby installation will be transferred and the Dbvisit Standby installation on the primary server will be overridden.This option can be used to test the transfer mechanism between the standby and primary server, where the standby server initiates the transfer instead of the primary server.

5. Resend a particular log.

dbvisit -r sequence_number <DDC>
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration.

Where sequence_number is a log sequence number. For more information see the Resending (archive) logs section.
For example:

Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Resend Sequence from Run Action drop-down menu > Run

Enter a sequence number.

6. Resynchronise with the standby database. This is used when the standby database has been rebuilt or Dbvisit Standby is not transferring the correct archive log sequence for the standby database.

dbvisit -R <DDC>
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration. For more information see the Re-synchronizing with the standby database section.

For example:

Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Resynchronize from Run Action drop-down menu > Run

7. To determine the archive log gap, and the transfer log gap, run Dbvisit Standby with the Inspect option.

dbvisit -i <DDC>

Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration.This produces the Dbvisit Standby log gap report. For more information, please see the Dbvisit Standby log gap report section.
For example:

Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Log Gap Report from Run Action drop-down menu > Run

8. To view or set the Dbvisit Standby license.

dbvisit -lic <DDC>
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a 
For more information see the Setting and viewing the Dbvisit Standby license key section.

Home > Setup > Register

9. Help and copyright information is available if Dbvisit Standby is run without parameters or options.

dbvisit
For example:

Stopping and starting databases

Dbvisit Standby includes commands to stop and start the databases. Dbvisit Standby will determine if the database is a primary or a standby database and will stop and start it accordingly. It can also open the standby database in read-only mode for reporting purposes.

10. To start a regular or standby database use:

dbv_oraStartStop start <DDC>
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration.

For example to start a standby database:

 Example to start a normal database:

Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Start Database from Run Action drop-down menu > Run

To start the standby database, choose the Standby Server tab.
It is recommended to use Dbvisit Standby to start the databases (primary and standby) automatically at boot time. Dbvisit Standby will start the databases automatically, and ensure that the primary and standby databases are started correctly. For Windows it is recommended to set the Windows services of the databases on both the primary and standby servers to manual. Please see Starting Databases automatically - Windows section for more information.

11. To stop (shutdown) a regular or standby database use:

dbv_oraStartStop stop <DDC>
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration.

For example to stop a standby database:

To stop (shutdown) a normal database:

Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Stop Database from Run Action drop-down menu > Run

To stop the standby database, choose the Standby Server tab.

12. To restart a database. This is the same as stopping a database first and then starting again:

dbv_oraStartStop restart <DDC>
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration.
Example:

Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Restart Database from Run Action drop-down menu > Run

To restart the standby database, choose the Standby Server tab.

13. To display the status of a database:

dbv_oraStartStop status <DDC>
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration.
For example:

Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Database Status from Run Action drop-down menu > Run

To show the status of the standby database, choose the Standby Server tab.

14. To open a standby database in read-only mode use:

dbv_oraStartStop open <DDC>
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration.
For example to open a standby database:

Home > Run > Run Interactive > Standby Server tab > select Database from drop-down menu > select Open Read-Only from Run Action drop-down menu > Run

When the standby database is in READ ONLY mode, the log files cannot be applied to the standby database. This means the standby database will not be in synch with the primary database.
To return to normal standby database mode for applying log files, the standby database needs to be restarted:

1. stop the database using dbv_oraStartStop stop <DDC>

2. Open

   

   image2012-1-22 17:6:43.png

   start the database using dbv_oraStartStop start <DDC>

     3. 

dbv_oraStartStop restart <DDC>

Activating standby database (failover)

In the event that the primary database is no longer available, the standby databases must be activated to become the new primary database. Dbvisit Standby provides a command to activate the standby database. For more information, please see the Failover - Activating the standby database section.

15. To activate a standby database:

dbv_oraStartStop activate <DDC> [Yes]
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration. Yes is optional and if specified then Dbvisit Standby will not prompt for confirmation to activate the standby database. This can be used for batch programming.
For example to activate a standby database:

Home > Run > Run Interactive > Standby Server tab > select Database from drop-down menu > select Activate from Run Action drop-down menu > Run

Graceful Switchover

16. To initial Graceful Switchover

dbv_oraStartStop switchover <DDC> [unique_key]
Where DDC is the name of the Dbvisit Database Configuration. In most cases this is the same as the database name. The DDC refers to the DDC file name which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration.unique_key is optional and can be supplied if Graceful Switchover is to be run in the background.This command must be issued on both the primary and the standby server.Both the primary and the standby database will be shutdown and restarted during the switchover. Please see the Graceful Switchover (role reversal) section for more information.

Example:
On the primary server start the Graceful Switchover procedure.

On the standby server start the Graceful Switchover procedure.

Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Graceful Switchover from Run Action drop-down menu > Run

Enter Unique Key. This can be any number, but it has to be the same number as entered on the Standby Server tab.

Home > Run > Run Interactive > Standby Server tab > select Database from drop-down menu > select Graceful Switchover from Run Action drop-down menu > Run

Enter Unique Key. This can be any number and it has to be the same number as entered on the Primary Server tab
.