dbvisit

Dbvisit help. Displays the dbvisit help pages.

dbvisit oracle_database

Normal Dbvisit operation. This command can be run on primary and standby servers.

Transfers log files from primary database if run on primary server.

Applies log files to standby database if run from standby server.

dbvisit -i oracle_database

Reports on the log sequences of:

1.  Latest archived log of primary database

2.  Latest non archived log of primary database (redo log)

3.  Latest log sequence of standby database

4.  Latest log sequence sent by Dbvisit

It also reports the Archive Log Gap which is the difference between the last archived log from the primary and the latest log sequence applied to the standby (1 minus 3) above.

No checkpoints are performed on the primary database, and no logs are transferred.

Every time this command is run, the information is inserted into Dbvisit repository table dbv_sequence_log. Reports can be produced from this table for Archive Log Gap analysis over time.

The standby database must be available in order to execute this command.

This command may be scheduled in cron on a regular basis to provide Archive Log Gap analysis data.

Can only be run on the primary server.

dbvisit -r sequence oracle_database

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

sequence is the log sequence number from which Dbvisit will start transferring logs until the current log.

Can only be run on the primary server.

See Resending Logs.

dbvisit -R oracle_database

Resynchronise primary database with standby database.

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

The standby database must be available in order to execute this command.

Can only be run on the primary server.

dbvisit -c oracle_database

Copy the Dbvisit installation and environment files to the standby server.

This function is performed automatically by Dbvisit every time it executes, except when SYNCH_DBVISIT_INSTALL is set to N for slow latency networks.

Can only be run on the primary server.

dbvisit -v oracle_database

Verbose option. Dbvisit will display trace information which may be required for support. The trace information will be saved to directory LOGDIR.

dbvisit -lic oracle_database

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

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

Can only be run on the primary server.

dbvisit -lic oracle_database licensed_user license

Sets the Dbvisit license for particular database. The license will be verified. If the license is correct, the words VALID will be displayed. 

Can only be run on the primary server.

dbvisit_setup

Run the dbvisit setup and configure utility. This can do the following:

1.  New setup (all options below except uninstall)

2.  Setup Dbvisit database configuration (DDC) file only

3.  Setup Archive log Management Module (AMM) only

4.  Setup Dbvisit Oracle user and repository only

5.  Upgrade of the Dbvisit repository

6.  Uninstall Dbvisit

Can only be run on the primary server.

dbv_oraStartStop start oracle_database

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

dbv_oraStartStop stop oracle_database

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

dbv_oraStartStop restart oracle_database

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

dbv_oraStartStop status oracle_database

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

dbv_oraStartStop open oracle_database

Opens the standby database in READONLY mode.

dbv_oraStartStop activate oracle_database

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 (available from version 5.0).

dbv_oraStartStop switchover oracle_database

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.

dbv_oraStartStop update_dbenv_file oracle_database

dbv_oraStartStop update_ddc_file oracle_database

Both commands are the same. Updates the database environment file dbv_oracle_database.env to allow Dbvisit to continue processing after graceful switchover. 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 database environment file is be updated.  

This procedure is part of normal graceful switchover processing and only needs to be initiated in special circumstances.

dbvisit dbvisitp

Run Dbvisit for database dbvisitp.

dbvisit_setup

Install and configure Dbvisit.

dbvisit -v dbvisitp

Run Dbvisit for database dbvisitp in verbose mode.

dbvisit -r 345 dbvisitp

Run Dbvisit starting at sequence 345 until the current sequence for database dbvisitp.

Standby Database does not need to be up and running.

dbvisit -R dbvisitp

Resynch. Contact the standby database to find the next sequence that it requires. Resend starting from this sequence for database dbvisitp.

Standby Database needs to be up and running.

dbvisit -i dbvisitp

Reports on the log sequences of database dbvisitp:

1.  Latest archived log of primary database

2.  Latest non archived log of primary database (redo log)

3.  Latest log sequence of standby database

4.  Latest log sequence sent by Dbvisit

5.  Archive Log Gap

dbvisit -lic dbvisitp

View the license status of database dbvisitp. The options are:

1. VALID - License is valid.
2. DEMO - Demo license that can be used for 30 days.
3. INVALID - Demo license has expired or license entered is not correct.

dbvisit -lic dbvisitp Avisit 3654

Set new license for licensed username Avisit and license number 3654 for database dbvisitp.

dbv_oraStartStop start dbvisitp

Start database dbvisitp.

dbv_oraStartStop status dbvisitp

Display the status of database dbvisitp.

dbv_oraStartStop switchover dbvisitp

Initiate graceful switchover between the primary and the standby database. The primary database transitions to a standby database and the standby database transitions to a primary database. There is no loss of data during the transition and the standby database does not have to be rebuilt.