Dbvisit Standby Configuration

In this section we will cover the creation of a new Dbvisit Standby Configuration, also known as creating a Dbvisit Database Configuration (DDC) file.

Once you have done a clean installation of Dbvisit Standby, the first step is to create a configuration file or DDC, which will contain information about your environment as well as your Primary and Standby database settings. For each Primary and Standby database pair there will be one DDC file. The file is created and maintained from the Primary server. The DDC file on the standby server is a mirrored copy of the one on the primary server and any changes to this file will be overwritten. The default location of the DDC file is in the “conf” directory located under the “standby” sub directory. If your Dbvisit Base directory is /usr/dbvisit, then you will fine the DDC files in the /usr/dbvisit/standby/conf directory. The DDC files have the following format: dbv_<DDC>.env, where DDC is in most cases the ORACLE_SID of your database, but this value can be different. Example names:

  • dbv_testdb.env : testdb is a single instance database environment

  • dbv_PROD1.env : PROD1 is the 1st instance in a 2 node RAC environment

  • dbv_PROD2.env : PROD2 is the 2nd instance in a 2 node RAC environment

The DDC file can be created from either the CLI or the GUI, but it should be done from the primary server. If you are using Oracle RAC you have to follow the same steps on all the Nodes in the Oracle RAC configuration.