Configure Dbvisit Standby (step 3) - Linux/Unix

Owned by KrupeshD (Deactivated)
Last updated: Jan 03, 2013Version comment
4 min read

Note: This step is only done on the Primary server(s)  or RAC nodes.

Once the Dbvisit Standby software is installed and SSH is configured, Dbvisit Standby can be configured (or setup) for a specific database.
Dbvisit Standby can be configured and run through a command line interface (CLI) or a web-based interface (GUI).
The CLI commands are indicated with a  and the web based or GUI commands are indicated with a
Dbvisit Standby is configured for each database using a menu based, command line, setup utility. This utility is called dbvisit_setup
The following applies to configuring Dbvisit Standby for a specific database:

  1. dbvisit_setup only needs to be run on the primary server. Not on the standby server.
  2. Dbvisit Standby will as much as possible determine the values for you. The default values will be shown in square brackets [ ]. If the default value is acceptable, then nothing needs to be entered, just press enter.
  3. After each entered variable, a confirmation will be given to ensure it is entered correctly.
  4. At the end of the setup process, an overview will be given for all variables entered, and any variable entered incorrectly can be altered.


Dbvisit Standby is configured for each database using a web-based menu. Specify the address of the primary server in the URL with the correct port (default 8081).

The following applies to configuring Dbvisit Standby GUI for a specific database:

1. Login to the Dbvisit Standby GUI interface by specifying the user name and password (default is admin/admin)

2. Choose Setup from the main menu.

3. Choose New Dbvisit Setup from the sub menu.

4. Setup only needs to be run on the primary server. Not on the standby server.

Configuration Outcome

The results of configuring Dbvisit Standby for a specific database are:

  1. The Dbvisit Standby Database Configuration (DDC) file is created. This is a text file equivalent to the init.ora and contains all the settings to enable Dbvisit Standby to keep the standby database up to date.
  2. Optionally the Dbvisit Standby Archive log Management Module (AMM) is configured. The settings for AMM are also contained in the DDC file.
  3. The Dbvisit Standby Database Repository (DDR) is created. This is a small repository created in the database to keep track of Dbvisit Standby processing.

RAC environment setup

In an Oracle RAC environment, dbvisit_setup is run on every primary node of the Oracle RAC cluster.
However during dbvisit_setup:

  • Choose option 1a in the main dbvisit_setup menu.
  • Choose the name of the instance as the ORACLE_SID and not the database name.

Please ensure the following prerequisites are met for RAC:

  • The archive destination for the primary RAC nodes must a shared location that is accessible by all primary RAC nodes.
  • If the standby is also a RAC cluster, then the archive destination location on the standby node must be accessible by all standby nodes in the RAC cluster.
  • The ARCHDEST destination where Dbvisit Standby will transfer the (archive) log files to on standby server should be the same for all primary RAC nodes.
  • The Dbvisit Standby Database Configuration file (DDC) created during the setup on each node will have the name of the instance and not the database (dbv_oracle_instance.env). If the database is called RACDB and has the following instances RACDB1 and RACDB2, the DDC files will be called:

dbv_RACDB1.env
dbv_RACBD2.env

  • Dbvisit Standby needs to be scheduled separately on each node. The name of the instance is used when installing and running Dbvisit Standby, not the name of the database. Example, to run Dbvisit Standby on one of the primary nodes:

     

    dbvisit RACDB1

  • Although not strictly necessary, it is advisable to ensure there is an entry in the oratab file for each RAC node. If the RAC nodes are called RACDB1 and RACDB2, and the database is called RACDB then the oratab (on each RAC node) should look like:

     

    RACDB:/oracle/orabase/product/10.2.0/db_1:N
    RACDB1:/oracle/orabase/product/10.2.0/db_1:N
    RACDB2:/oracle/orabase/product/10.2.0/db_1:N 
  • With a single instance standby database, Dbvisit Standby is scheduled on the standby server using the instance name from one of the primary nodes. Example: if the RAC configuration has 2 instances called RACDB1 and RACDB2 and the standby database is called RACDB, then Dbvisit Standby is executed on the standby server using the command: dbvisit RACDB1