...
On the Standby Server, Dbvisit Standby will pickup the transferred archive logs and apply them to the standby database
If configured, Dbvisit Standby can also manage the archive logs on the standby server; example purge logs older than specified time
...
Dbvisit Standby functionality can be summarized as follows:
Archive log extraction from primary database
Secure transfer of archive logs between primary and standby servers
Apply of archive logs to the standby database
Easy role reversal (switchover) between primary and standby databases
Easy activation of a standby database in case of disaster
Full support for Oracle Real Application Clusters (RAC)
Support for one primary database having multiple standby databases
Recover standby database using a delay (LAG)
Recover standby to specified SCN or Timestamp
Archive logs compression during transfer
Archive log Management Module (AMM)
Maintain archive logs on both primary and standby
Delete logs older then specified time
Compress archive logs that was already applied
Automated process to create the standby database (CSD)
Automated process to re-synchronize the standby database due to:
Unrecoverable Archive log gap
No-Logging operations
Reporting options include:
Archive log transfer gap reporting
Archive log apply gap reporting
Command line interface (CLI) and Graphical User Interface (GUI) is available
...
The Dbvisit Standby version 7 environment consists of the following key components:
...
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 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:
...
...
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 to send/apply logs, as well as 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
...