Dbvisit Standby Command Reference

Owned by Anton Els (Deactivated)
Last updated: Jan 27, 2014 by Anna Macnaughtan (Deactivated)

The following list gives an overview of the Dbvisit Standby commands available in the command line interface (CLI).
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.

Convention

"<>"

"[ ]"

Commands shown in "< >" are supplied by the user and are not optional. Do not include the "< >" as part of the command.

Commands shown in square brackets are optional commands. Do not include the "[ ]" as part of the command.

The commands outlined below will work the same on Linux and Windows based systems.

 

 

Command

Description

dbvisit 
dbvisit -h
dbvisit -?

If the “dbvisit” command is executed in either one of these three methods, the Dbvisit Standby help pages will be displayed.

Example:

oracle@dbvlin101[/usr/dbvisit/standby]: ./dbvisit -h
NAME
     Dbvisit Standby
              - Oracle Standby Database Technology.
              - Automated managed Standby Databases.
              - Automatic creation of Standby Databases.
              - Oracle Disaster Recovery.
  VERSION
       Version 7.0.04.11727
  USAGE
       dbvisit <DDC>
       dbvisit -r <SEQUENCE_NUMBER> <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 -?
       dbvisit_setup
       dbv_functions
  CONVENTIONS
       Lowercase/Mixed Case is Dbvisit Standby key word.
       <UPPERCASE> is user supplied value. Do not include < > in value.
       [] is optional supplied value. Do not include [ ] in value.
  DDC
       DDC is the name of the Dbvisit Database Configuration.
       In most cases this is the same as the database name or ORACLE_SID.
       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.
..
..
..
dbvisit <DDC>

This command is used to execute Normal Dbvisit Standby operation. This command is run on primary and standby servers using the exact same command, but

  • Transfers log files from primary database if run on primary server
  • Applies log files to standby database if run from standby server

Example (Primary Server):

When this command is executed on the primary server, archive logs will be shipped (copied) to the standby server.

oracle@dbvlin101[/usr/dbvisit/standby]: ./dbvisit devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11727) (pid 1837)
dbvisit started on dbvlin101: Thu Jan 23 15:15:27 2014 ()
=============================================================


>>> Sending heartbeat message... - done.


>>> Checking Dbvisit Standby for configurational differences between dbvlin101 and
    dbvlin102...
    No configurational differences found between dbvlin101 and dbvlin102.


>>> Log file(s) for devdb will be transferred from dbvlin101 to dbvlin102...
  > Transferring 'o1_mf_1_451_9fyvw31c_.arc.gz' to server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [12172 KB/s] - done.
  > Transferring 'o1_mf_1_452_9fyxnrtb_.arc.gz' to server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [10620 KB/s] - done.
  > Transferring 'o1_mf_1_453_9fz257do_.arc.gz' to server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [10664 KB/s] - done.


    3 archive log transfers to dbvlin102 for devdb completed.
    Last sequence was 453.


    No Mail sent as SEND_MAIL_FLAG = N
>>> Dbvisit Archive Management Module (AMM)
    Config: number of archives to keep      = 0
    Config: number of days to keep archives = 7
    Config: archive backup count            = 0
    Config: diskspace full threshold        = 80%

    Current disk percent full (/u01/app/oracle/fast_recovery_area) = 66%


    Number of archive logs deleted = 10
=============================================================
dbvisit ended on dbvlin101: Thu Jan 23 15:15:54 2014
=============================================================

 

Example (Standby Server):


When this command is executed on the standby server, archive logs will be applied. Example output below:

oracle@dbvlin102[/usr/dbvisit/standby]: ./dbvisit devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11727) (pid 17049)
dbvisit started on dbvlin102: Thu Jan 23 15:15:56 2014 ()
=============================================================
>>> Sending heartbeat message... - done.


>>> Log file(s) for devdb from dbvlin101 will be applied to dbvlin102
201401231515 - Log seq 450 thread 1 applied to standby database devdb.
201401231515 - Log seq 451 thread 1 applied to standby database devdb.
201401231515 - Log seq 452 thread 1 applied to standby database devdb.
201401231515 - Log seq 453 thread 1 applied to standby database devdb.

    No Mail sent as SEND_MAIL_FLAG_DR = N


>>> Dbvisit Archive Management Module (AMM)
    Config: number of archives to keep      = 0
    Config: number of days to keep archives = 7
    Config: diskspace full threshold        = 80%


Processing /u01/app/oracle/archive/devdb...
    Archive log dir: /u01/app/oracle/archive/devdb
    Total number of archive files   : 26
    Number of archive logs deleted = 13
    Current Disk percent full       : 63%
=============================================================
dbvisit ended on dbvlin102: Thu Jan 23 15:16:17 2014
=============================================================

 

 

dbvisit -i <DDC>

This command will execute the “Log Gap Report”. 

The Log Gap Report provides an overiew of the current standby configuration status and include information such as:

  • Latest archived log sequence of primary database
  • Latest non archived log sequence of primary database (redo log)
  • Latest log sequence applied to the standby database
  • Latest log sequence that as sent from primary to by Dbvisit Standby

Other information provided by the report include:

  • Archive log gap which is difference between the last archived sequence on the primary and the last applied sequence on the standby database. The archive log gap should be near 0 (except when APPLY_DELAY_LAG_MINUTES is used).
  • Transfer log gap which is the difference between the last archived sequence on the primary and the last sequence transferred to the standby server. The transfer log gap should be near 0.

When this command is executed, no log switches are performed on the primary database, and no logs are transferred to the standby database.  This command is purely used for reporting information from the primary/standby configuration for the specified DDC file.

Every time this command is run, the information is inserted into Dbvisit Standby database repository (DDR) table dbv_sequence_log. Reports can be produced from this table for trend analysis over time.

Dbvisit Standby will start the standby database if the standby database is not running and AUTO_START_STANDBY_DB = Yes (default)

This command may be scheduled in CRON or other scheduler on a regular basis to provide Dbvisit Standby log gap analysis data over time.

Note that this command can only be run on the primary server

Example:

oracle@dbvlin101[/usr/dbvisit/standby]: ./dbvisit -i devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11727) (pid 2738)
dbvisit started on dbvlin101: Thu Jan 23 15:20:36 2014 ()
=============================================================


Dbvisit Standby log gap report for devdb at 201401231520:
-------------------------------------------------------------
Standby database on dbvlin102 is at sequence: 453.
Primary database on dbvlin101 is at log sequence: 455.
Primary database on dbvlin101 is at archived log sequence: 454.
Dbvisit Standby last transfer log sequence: 454.
Dbvisit Standby last transfer at: 201401231520.


Archive log gap for devdb:  1.
Transfer log gap for devdb: 0.
Standby database time lag (HH:MI:SS): 17:20:20.
    No Mail sent as SEND_MAIL_FLAG = N

=============================================================
dbvisit ended on dbvlin101: Thu Jan 23 15:20:42 2014
=============================================================
dbvisit -r <sequence> <DDC>

Specific archived log and all subsequent archived logs will be resend to the standby database.

The <sequence> is the log sequence number from which Dbvisit Standby will start transferring logs until the current log.

Can only be run on the primary server.

 

Example:

Resending all archived logs from log sequence 451 to the standby database:

oracle@dbvlin101[/usr/dbvisit/standby]: ./dbvisit -r 451 devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11727) (pid 2873)
dbvisit started on dbvlin101: Thu Jan 23 15:24:06 2014 ()
=============================================================
    Waiting 3 seconds for log switch completion...


>>> Checking Dbvisit Standby for configurational differences between dbvlin101 and
    dbvlin102...
    No configurational differences found between dbvlin101 and dbvlin102.


>>> Log file(s) for devdb will be transferred from dbvlin101 to dbvlin102...
  > Transferring 'o1_mf_1_451_9fyvw31c_.arc.gz' to server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [11772 KB/s] - done.
  > Transferring 'o1_mf_1_452_9fyxnrtb_.arc.gz' to server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [10959 KB/s] - done.
  > Transferring 'o1_mf_1_453_9fz257do_.arc.gz' to server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [10668 KB/s] - done.
  > Transferring 'o1_mf_1_454_9g0z30yp_.arc.gz' to server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [10250 KB/s] - done.
  > Transferring 'o1_mf_1_455_9g0zb84d_.arc.gz' to server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [7508 KB/s] - done.


    5 archive log transfers to dbvlin102 for devdb completed.
    Last sequence was 455.
    No Mail sent as SEND_MAIL_FLAG = N


>>> Dbvisit Archive Management Module (AMM)
    Config: number of archives to keep      = 0
    Config: number of days to keep archives = 7
    Config: archive backup count            = 0
    Config: diskspace full threshold        = 80%


    Current disk percent full (/u01/app/oracle/fast_recovery_area) = 66%


    Number of archive logs deleted = 0

=============================================================
dbvisit ended on dbvlin101: Thu Jan 23 15:24:29 2014
=============================================================

 

 

dbvisit -R <DDC>

This command also knows as the process to "resyncing" the archive logs as well as the Dbvisit Standby configuration (DDC) file.

Dbvisit Standby will connect to the standby database and determine the next log sequence which needs to be applied. This required archived log and all subsequent logs will be transferred from the primary database until the current log.

In addition to this the Primary server DDC file will also be copied to the Standby server.

The standby database must be available in order to execute this command. Can only be run on the primary server.

dbvisit -c <DDC>

Copy the Dbvisit Standby configuration (DDC) file from the primary server to the standby server.

This function is performed automatically by Dbvisit Standby every time it executes depending on setting SYNCH_DBVISIT_INSTALL.

Can only be run on the primary server.

Dbvisit Standby configuration file (DDC) will be overridden on the standby server.

Example:

oracle@dbvlin101[/usr/dbvisit/standby]: ./dbvisit -c devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11727) (pid 3487)
dbvisit started on dbvlin101: Thu Jan 23 15:31:42 2014 ()
=============================================================


  > Transferring 'dbv_devdb.env' to server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [9533 KB/s] - done.

=============================================================
dbvisit ended on dbvlin101: Thu Jan 23 15:31:50 2014
=============================================================
dbvisit -c <DDC <nocksum>

 

This command is the same as "dbvisit -c <DDC>" mentioned above, but it does not perform a checksum comparison between the original file (or executable) and the transferred file (or executable).

dbvisit -lic <DDC>

Displays the Dbvisit Standby license for a particular database. This can be VALID, INVALID or DEMO.

When the DEMO license has expired, a Dbvisit Standby license must be purchased in order to continue to use Dbvisit Standby.

Can only be run on the primary server.

Example:

oracle@dbvlin101[/usr/dbvisit/standby]: ./dbvisit -lic devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11727) (pid 3558)
dbvisit started on dbvlin101: Thu Jan 23 15:33:38 2014 ()
=============================================================
Dbvisit Standby license information for: devdb
customer_seq=1
customer_key_seq=0
license_type=DEMO (0)
expiry_date=2014-02-10
Status: Valid
=============================================================
dbvisit ended on dbvlin101: Thu Jan 23 15:33:39 2014
=============================================================
dbvisit -lic <DDC> <license_key>

Sets the Dbvisit Standby license for particular database. The license will be verified. If the license is correct, the words "Status: Valid" will be displayed. 

Can only be run on the primary server.

 

Example: (note license below is only for demo)

oracle@dbvlin101[/usr/dbvisit/standby]: ./dbvisit -lic devdb EB57I-DYK7K-9PI2V-1SH0D-AAWGR-2WEDY-ZJJ0F
=============================================================
Dbvisit Standby Database Technology (7.0.03.11667) (pid 6953)
dbvisit started on dbvlin101: Fri Jan 10 13:46:35 2014 ()
=============================================================
Dbvisit Standby license information for: devdb
customer_seq=1
customer_key_seq=0
license_type=DEMO (0)
expiry_date=2014-02-10
=>Update with license key: EB57I-DYK7K-9PI2V-1SH0D-AAWGR-2WEDY-ZJJ0F? <Yes/No> [Yes]: YES
License updated.
Status: Valid
=============================================================
dbvisit ended on dbvlin101: Fri Jan 10 13:46:51 2014
=============================================================
dbvisit_setup

Run the Dbvisit Standby setup and configure utility from where steps such as the following can be performed using a menu driven option:

  • New database or RAC Instance setup
  • Create standby database
  • New Dbvisit Standby Database Configuration (DDC) file setup
  • New Dbvisit Standby Archive log Management Module (AMM) setup
  • New Dbvisit Standby database repository (DDR) setup
  • Manage the database repository (DDR) 
  • Update Dbvisit Standby Database Configuration (DDC) file
  • Synchronise Standby Database (using incremental RMAN backups)
  • Uninstall Dbvisit Standby

This command should only be executed from the primary server

 

Example:

oracle@dbvlin101[/usr/dbvisit/standby]: ./dbvisit_setup

=========================================================
Dbvisit Standby Database Technology (7.0.04.11726)
 http://www.dbvisit.com


=========================================================
=>dbvisit_setup only needs to be run on the primary server.
Is this the primary server? <Yes/No> [Yes]:

=========================================================
 Dbvisit Standby Database Technology (7.0.04.11726)
      http://www.dbvisit.com
 Dbvisit Database setup
 Default values will be shown in []


Options:
   1) New Dbvisit Database setup (combines options 2,3,4)
   1a) New Dbvisit RAC Instance setup (combines options 2,3,4)
   
   2) New Dbvisit Database configuration (DDC) file setup
   3) New Dbvisit Archive Management Module (AMM) setup
   4) New Dbvisit Database repository (DDR) setup
   
   5) Manage Dbvisit Database repository (DDR)
   6) Update Dbvisit Database configuration (DDC) file
   
   7) Create Standby Database (and template)
   8) Synchronize Standby Database
   
   9) Uninstall Dbvisit Database repository (DDR)
   E) Exit
=========================================================
Please enter choice :
 

 

 

dbv_oraStartStop start <DDC>

You can use the dbv_oraStartStop command to start the database. This may be either a regular (primary) database or a standby database. Dbvisit Standby will determine if the database is a primary or a standby database and will start it accordingly.

Example (starting primary):

oracle@dbvlin101[/usr/dbvisit/standby]: ./dbv_oraStartStop start devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11619) (pid 4059)
dbv_oraStartStop started on dbvlin101: Thu Jan 23 15:51:43 2014 ()
=============================================================
Starting Regular Database devdb...
Regular Database devdb started .
=============================================================
dbv_oraStartStop ended on dbvlin101: Thu Jan 23 15:51:52 2014
=============================================================

 

Example (starting standby):

oracle@dbvlin102[/usr/dbvisit/standby]: ./dbv_oraStartStop start devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11619) (pid 17599)
dbv_oraStartStop started on dbvlin102: Thu Jan 23 15:49:10 2014 ()
=============================================================
Starting Standby Database devdb...
Standby Database devdb started .
=============================================================
dbv_oraStartStop ended on dbvlin102: Thu Jan 23 15:49:18 2014
=============================================================

 

 

dbv_oraStartStop stop <DDC>

Stops (shutdown) the database. This may be either a regular (primary) database or a standby database. Dbvisit Standby will determine if the database is a primary or a standby database and will start it accordingly.

Example (primary server):

oracle@dbvlin101[/usr/dbvisit/standby]: ./dbv_oraStartStop stop devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11619) (pid 3762)
dbv_oraStartStop started on dbvlin101: Thu Jan 23 15:48:41 2014 ()
=============================================================
Shutting down regular Database devdb...
Regular Database devdb shutdown successfully.
=============================================================
dbv_oraStartStop ended on dbvlin101: Thu Jan 23 15:49:24 2014
=============================================================

 

Example (standby server):

oracle@dbvlin102[/usr/dbvisit/standby]: ./dbv_oraStartStop stop devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11619) (pid 17548)
dbv_oraStartStop started on dbvlin102: Thu Jan 23 15:48:54 2014 ()
=============================================================
Shutting down standby Database devdb...
Standby Database devdb shutdown successfully.
=============================================================
dbv_oraStartStop ended on dbvlin102: Thu Jan 23 15:48:55 2014
=============================================================
dbv_oraStartStop restart <DDC>

Stops (shutdown) and then starts the database. This may be either a regular (primary) database or a standby database. Dbvisit Standby will determine if the database is a primary or a standby database and will stop and start it accordingly.

Example (Primary Server):

oracle@dbvlin101[/usr/dbvisit/standby]: ./dbv_oraStartStop restart devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11619) (pid 4383)
dbv_oraStartStop started on dbvlin101: Thu Jan 23 15:56:14 2014 ()
=============================================================
Shutting down regular Database devdb...
Regular Database devdb shutdown successfully.
Starting Regular Database devdb...
Regular Database devdb started .
=============================================================
dbv_oraStartStop ended on dbvlin101: Thu Jan 23 15:57:01 2014
=============================================================

 

Example (Standby Server):

oracle@dbvlin102[/usr/dbvisit/standby]: ./dbv_oraStartStop restart devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11619) (pid 17860)
dbv_oraStartStop started on dbvlin102: Thu Jan 23 15:56:19 2014 ()
=============================================================
Shutting down standby Database devdb...
Standby Database devdb shutdown successfully.
Starting Standby Database devdb...
Standby Database devdb started .
=============================================================
dbv_oraStartStop ended on dbvlin102: Thu Jan 23 15:56:27 2014
=============================================================

 

 

dbv_oraStartStop status <DDC>

Displays the status of the database. This can be either a regular (primary) database or a standby database.

Example (Primary Server):

oracle@dbvlin101[/usr/dbvisit/standby]: ./dbv_oraStartStop status devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11619) (pid 4922)
dbv_oraStartStop started on dbvlin101: Thu Jan 23 15:58:02 2014 ()
=============================================================
Regular Database devdb on dbvlin101 is up.
=============================================================
dbv_oraStartStop ended on dbvlin101: Thu Jan 23 15:58:02 2014
=============================================================

 

Example (Standby Server):

oracle@dbvlin102[/usr/dbvisit/standby]: ./dbv_oraStartStop status devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11619) (pid 18121)
dbv_oraStartStop started on dbvlin102: Thu Jan 23 15:57:55 2014 ()
=============================================================
Standby Database devdb on dbvlin102 is up.
=============================================================
dbv_oraStartStop ended on dbvlin102: Thu Jan 23 15:57:56 2014
=============================================================
dbv_oraStartStop open <DDC>

Opens the standby database in READONLY mode. To change the standby from read-only mode to recovery mode, run "dbv_oraStartStop restart <DDC>"

Example (Standby Server):

oracle@dbvlin102[/usr/dbvisit/standby]: ./dbv_oraStartStop open devdb
=============================================================
Dbvisit Standby Database Technology (7.0.04.11619) (pid 18171)
dbv_oraStartStop started on dbvlin102: Thu Jan 23 15:59:35 2014 ()
=============================================================
Open Standby Database devdb in READ ONLY mode...
Standby Database devdb opened in READ ONLY mode.
Log files cannot be applied to Database while in READ ONLY mode.
Database tempfile(s) may need to be added to this database.
=============================================================
dbv_oraStartStop ended on dbvlin102: Thu Jan 23 15:59:39 2014
=============================================================
dbv_oraStartStop activate <DDC> [Yes]

In the event the primary database is no longer available. Activates the standby database to become a primary database. Activation cannot be reversed. A new standby database will have to be built.

To disable the prompt to confirm that the database can be activated specify Yes on the command line.

dbv_oraStartStop switchover <DDC> [unique_key]

Initiates the Graceful Switchover process to transition the primary database to a standby database and the standby database to a primary database. This command must be given on both the primary and the standby servers.

There is no loss of data during the transition and the standby database does not have to be rebuilt.

To run in batch mode, a unique key can be specified on the command line. This unique key must be the same on both the primary and standby server and can be any number not used before.

dbv_oraStartStop update_ddc_file <DDC>

Updates the Dbvisit Standby Database Configuration (DDC) file dbv_<DDC>.env to allow Dbvisit Standby to continue processing after Graceful Switchover or when activating the standby database to become the new primary database. All variables associated with the transition from the primary database to the standby database will be updated automatically. A backup copy (which is time stamped) will be made before the Dbvisit Standby Database Configuration (DDC) file is be updated. 

This option is part of normal Graceful Switchover processing.

dbv_functions -h 

Brings up help for dbv_functions. This performs various Dbvisit Standby functions like compression, copying, repository reporting, creating control file, list %full Diskspace, checksum etc. This utility may also be used on its own.