- The Dbvisit Standby environment (described above) will be the same on both the primary and the standby server. The Dbvisit Standby software executes separately on the primary and standby servers.
- DDC name or simply DDC. Most Dbvisit Standby commands require the DDC. In most cases this is the same as the database name or ORACLE_SID. The DDC refers to the DDC file which is in the form: dbv_DDC.env and contains the Dbvisit Standby settings for a particular primary and standby configuration. The DDC and the ORACLE_SID can be different. The ORACLE_SID is a variable setting contained within the DDC file and is not linked to the DDC name. However in most cases the DDC and the ORACLE_SID are the same.
Example: If the database name (or ORACLE_SID) is orcl, then the DDC is orcl and the DDC file is dbv_orcl.env.
- A primary and standby database must be on separate servers. A primary and standby database on the same server is not supported.
- Each time Dbvisit Standby executes, the DDC file on the primary server is compared with the DDC file on the standby server. If there are any differences, the DDC file on the standby server will be overwritten with the DDC file of the primary server. This is why the DDC file should only be edited on the primary server.
Dbvisit Standby is scheduled on both the primary and the standby server. The schedule determines the maximum lag of the standby database. For example, if Dbvisit Standby is scheduled every 5 minutes, then the maximum time the standby database is behind the primary database is 5 minutes.
- Dbvisit Standby can be configured and run through a command line interface (CLI) or a web-based interface (GUI). Throughout this user manual the CLI commands will be indicated with a
and the web based or GUI commands will be indicated with a 