Page Comparison

Dbvnet

(Dbvisit Networking)

Dbvisit Standby Version 7

introduces a new component called Dbvnet.  
This component is responsible for the secure communication between the primary and standby systems.

 It consists of the following executable:

•  dbvnet - This is the main Dbvnet executable used to start the networking communcation communication between the primary and standby server. This component should run on both the primary and standby servers and is configured during the installation process.

Dbvserver

(Dbvisit Standby GUI)

This is a Web server that provides the web interface to Dbvisit. 
It consists of the following executable:

• dbvserverd - The main Dbvserver executable for the Dbvisit Web server, and is used to start/stop the Dbvisit Web server.

Standby

(Dbvisit Standby Core and CLI)

Dbvisit Standby, also referred to as Standby, is the core of the Dbvisit Standby product. 
This

consists of the following executables (commands):

• dbvisit - The main Dbvisit Standby executable, including functionality include to send/apply logs, as well as generating generate reports.
• dbv_oraStartStop - Executable to start, stop, failover and switchover the databases.
• dbvisit_setup - Menu driven wizard to configure Dbvisit and to create the standby database.
• dbv_functions - Executable to provide extra tools and functionality.

Dbvisit Database Configuration

(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

by 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

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, and the default schema name is dbvisit7.

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