Page Comparison

Dbvisit Standby refers to the product "Dbvisit Standby" and does not refer to the standby database or standby server.

The Dbvisit Standby environment consists of the following components:

1. Dbvisit software:
   1. Dbvisit Standby. This consists of the following executables:
      1. dbvisit - The main Dbvisit Standby executable.
      2. dbv_oraStartStop - Executable to start, stop, failover and switchover the databases.
      3. dbvisit_setup - Menu driven wizard to configure Dbvisit and to create the standby database.
      4. dbv_functions - Executable to provide extra tools and functionality.
   2. Dbvserver. This is Web server that provides the web interface to Dbvisit. It consists of the following executable:
      1. dbvserverd - The main Dbvserver executable for the Dbvisit Web server.
2. Dbvisit Database Configuration file or DDC file. This is similar to the init.ora parameter file and contains the Dbvisit Standby settings for a specific primary and standby database pair. The DDC file is generated during setup for each database. The DDC file can be edited with any text editor or through running dbvisit_setup or through the web-based GUI. The DDC file should only be edited on the primary server. The template to create the DDC file for each database is dbv_ORACLE_SID.env.
3. Dbvisit Database Repository (DDR). This is a schema in the database that contains the Dbvisit Standby tables used to manage the standby process. The DDR is created during setup.
4. Dbvisit Standby trace files. Each time Dbvisit Standby executes, a trace file is generated. This trace file contains information about Dbvisit Standby processing and its environment. This trace file is used by the Dbvisit support team to diagnose issues. When an alert or error notification is sent by Dbvisit Standby, the trace file will be attached to the email so that this can be forwarded to Dbvisit support if needed.