Dbvisit standby
Author: m | 2025-04-24
Dbvisit Support; Dbvisit Standby; Dbvisit Standby Releases; Dbvisit Standby Releases ★ Dbvisit Standby MultiPlatform 11.7.3 () Released ★ Dbvisit Standby MultiPlatform 11.7.2 ( ) Released ★ Dbvisit Standby MultiPlatform 11.7.1 ( ) Released ★ Dbvisit Standby MultiPlatform 11.7.0 ( ) Released Dbvisit Standby v9 Support Matrix; Dbvisit Standby License; Installing Dbvisit Standby; Upgrade Dbvisit Standby; Creating the DDC File; DDC File Reference; Create Standby Database (CSD) Creating two standby databases on same server; Cascading Standby Databases with Dbvisit Standby; Dbvisit Standby Command Line Interface (CLI) Dbvisit Standby
Installing Dbvisit Standby - Dbvisit Standby 10.0 User Guide - Dbvisit
Executed on the primary, will initiate Dbvisit Standby on the standby server as the last step of running Dbvisit Standby on the primary server. will mean Dbvisit Standby should no longer be scheduled on the standby server (as it is now initiated from the primary server). Dbvisit Standby will no longer function as two independent processes with independent alerting and a new strategy must be in place to ensure that notification is received in case of a failure. It is therefore recommended to set ARCHIVE_LOG_GAP_THRESHOLD or TRANSFER_LOG_GAP_THRESHOLD and to schedule, the Dbvisit Standby log gap report (dbvisit -i) on the primary to alert if the standby database gets too far behind the primary database.Warning: Only set this to Y if you understand the implications and make sure you test this in your specific configuration.Possible Values are Y or N.Example:INITIATE_DBVISIT_ON_STANDBY=NLOCK_MAX_TIME_SECIf Dbvisit Standby detects a lock on a file that it is trying to process, this parameter specifies the maximum wait in seconds Dbvisit Standby will retry the lock.If the file is still locked after LOCK_MAX_TIME_SEC, then Dbvisit Standby will raise an alert.Example:LOCK_MAX_TIME_SEC=10LOCK_RETRY_TIMEOUT_MILLISECIf Dbvisit Standby detects a lock on a file that it is trying to process, this parameter specifies the wait in milliseconds before Dbvisit Standby will attempt to access the file again. On some platforms the minimum timeout time may be 1 second.Example:LOCK_RETRY_TIMEOUT_MILLISEC=500LOG_FILE_ROTATE_MAXDbvisit Standby log files are will automatically according to these settings.LOG_FILE_SIZE_MAX_MBLOG_FILE_ROTATE_MAX indicates how many backups are made of the log files before it is overwritten.The first backup will. Dbvisit Support; Dbvisit Standby; Dbvisit Standby Releases; Dbvisit Standby Releases ★ Dbvisit Standby MultiPlatform 11.7.3 () Released ★ Dbvisit Standby MultiPlatform 11.7.2 ( ) Released ★ Dbvisit Standby MultiPlatform 11.7.1 ( ) Released ★ Dbvisit Standby MultiPlatform 11.7.0 ( ) Released Dbvisit Standby v9 Support Matrix; Dbvisit Standby License; Installing Dbvisit Standby; Upgrade Dbvisit Standby; Creating the DDC File; DDC File Reference; Create Standby Database (CSD) Creating two standby databases on same server; Cascading Standby Databases with Dbvisit Standby; Dbvisit Standby Command Line Interface (CLI) Dbvisit Standby Dbvisit Standby MulitPlatform 11.0 ( ) Released; Dbvisit Standby MultiPlatform 11.7.0 ( ) Released; Dbvisit Standby MultiPlatform 11.7.1 ( ) Released; Dbvisit Standby MultiPlatform 11.5.0 ( ) Released; Dbvisit Standby Version Support Matrix Dbvisit Standby MulitPlatform 11.0 ( ) Released; Dbvisit Standby MultiPlatform 11.7.0 ( ) Released; Dbvisit Standby MultiPlatform 11.7.1 ( ) Released; Dbvisit Standby MultiPlatform 11.5.0 ( ) Released; Dbvisit Standby Version Support Matrix Cascading Standby Databases with Dbvisit Standby; Dbvisit Standby Components. Dbvisit Standby Command Line Interface (CLI) Using the Central Console - Dbvserver; Dbvisit Standby Networking - Dbvnet; Dbvisit Standby Agent - Dbvagent; Dbvisit Standby Basic Features. Graceful Switchover (GS) Activate (Failover) as Standby Database Dbvisit Standby Releases ★ Dbvisit Standby MultiPlatform 11.7.3 () Released ★ Dbvisit Standby MultiPlatform 11.7.2 ( ) Released ★ Dbvisit Standby MultiPlatform 11.7.1 ( ) Released ★ Dbvisit Standby MultiPlatform 11.7.0 ( ) Released ★ Dbvisit Standby MultiPlatform 11.6.0 ( Dbvisit Standby Releases ★ Dbvisit Standby MultiPlatform 11.7.3 () Released ★ Dbvisit Standby MultiPlatform 11.7.2 ( ) Released ★ Dbvisit Standby MultiPlatform 11.7.1 ( ) Released ★ Dbvisit Standby MultiPlatform 11.7.0 ( ) Released ★ Dbvisit Standby MultiPlatform 11.6.0 ( Be dbvisit_hist.log.1The second backup will be dbvisit_hist.log.2etc.LOG_FILE_SIZE_MAX_MB indicates the size of the log file before the log file is rotated as above. Example:LOG_FILE_ROTATE_MAX = 5LOG_FILE_SIZE_MAX_MB = 5LOG_SWITCH_WAIT_IN_SECWait in seconds to allow log switch to occur. If it is found that the archives are not yet completely written to when Dbvisit Standby tries to transfer them to the standby server, then this parameter may be increased. If Oracle has not completed the log switch before Dbvisit Standby attempts to compress and transfer the logs, Dbvisit Standby will raise an error message.Default value: 3Example: LOG_SWITCH_WAIT_IN_SEC=3MAX_TIMES_TRIEDSpecifies the number of times that Dbvisit Standby should attempt to apply the missing log file before raising an error.Note this number is also used to raise an error if Dbvisit Standby cannot be started in case a previous scheduled Dbvisit Standby is still running.Ensure that this number is not too low and not too high.If you are unsure, set the value to 3 and increase to 6 or 9 as needed.Example (default) value:MAX_TIMES_TRIED = 3MIN_ARCH_TO_KEEPNumber of archive logs Dbvisit AMM module keeps on the server when deleting logs, regardless of AMM settingsThe default value is 3NUM_TRACE_TO_KEEPSpecifies the number of Dbvisit Standby trace files to keep. Trace files are generated every time Dbvisit Standby is executed. Trace files are only used for Dbvisit support. Dbvisit Standby will delete trace files greater than this number. Deletes oldest trace file first. Works in conjunction with DAYS_TO_KEEP_TRACE.Least restrictive setting applies between DAYS_TO_KEEP_TRACE and NUM_TRACE_TO_KEEPTo turn off, set to 0.Example:NUM_TRACE_TO_KEEP=100REMOVE_TEMP_FILESDetermines if DbvisitComments
Executed on the primary, will initiate Dbvisit Standby on the standby server as the last step of running Dbvisit Standby on the primary server. will mean Dbvisit Standby should no longer be scheduled on the standby server (as it is now initiated from the primary server). Dbvisit Standby will no longer function as two independent processes with independent alerting and a new strategy must be in place to ensure that notification is received in case of a failure. It is therefore recommended to set ARCHIVE_LOG_GAP_THRESHOLD or TRANSFER_LOG_GAP_THRESHOLD and to schedule, the Dbvisit Standby log gap report (dbvisit -i) on the primary to alert if the standby database gets too far behind the primary database.Warning: Only set this to Y if you understand the implications and make sure you test this in your specific configuration.Possible Values are Y or N.Example:INITIATE_DBVISIT_ON_STANDBY=NLOCK_MAX_TIME_SECIf Dbvisit Standby detects a lock on a file that it is trying to process, this parameter specifies the maximum wait in seconds Dbvisit Standby will retry the lock.If the file is still locked after LOCK_MAX_TIME_SEC, then Dbvisit Standby will raise an alert.Example:LOCK_MAX_TIME_SEC=10LOCK_RETRY_TIMEOUT_MILLISECIf Dbvisit Standby detects a lock on a file that it is trying to process, this parameter specifies the wait in milliseconds before Dbvisit Standby will attempt to access the file again. On some platforms the minimum timeout time may be 1 second.Example:LOCK_RETRY_TIMEOUT_MILLISEC=500LOG_FILE_ROTATE_MAXDbvisit Standby log files are will automatically according to these settings.LOG_FILE_SIZE_MAX_MBLOG_FILE_ROTATE_MAX indicates how many backups are made of the log files before it is overwritten.The first backup will
2025-04-02Be dbvisit_hist.log.1The second backup will be dbvisit_hist.log.2etc.LOG_FILE_SIZE_MAX_MB indicates the size of the log file before the log file is rotated as above. Example:LOG_FILE_ROTATE_MAX = 5LOG_FILE_SIZE_MAX_MB = 5LOG_SWITCH_WAIT_IN_SECWait in seconds to allow log switch to occur. If it is found that the archives are not yet completely written to when Dbvisit Standby tries to transfer them to the standby server, then this parameter may be increased. If Oracle has not completed the log switch before Dbvisit Standby attempts to compress and transfer the logs, Dbvisit Standby will raise an error message.Default value: 3Example: LOG_SWITCH_WAIT_IN_SEC=3MAX_TIMES_TRIEDSpecifies the number of times that Dbvisit Standby should attempt to apply the missing log file before raising an error.Note this number is also used to raise an error if Dbvisit Standby cannot be started in case a previous scheduled Dbvisit Standby is still running.Ensure that this number is not too low and not too high.If you are unsure, set the value to 3 and increase to 6 or 9 as needed.Example (default) value:MAX_TIMES_TRIED = 3MIN_ARCH_TO_KEEPNumber of archive logs Dbvisit AMM module keeps on the server when deleting logs, regardless of AMM settingsThe default value is 3NUM_TRACE_TO_KEEPSpecifies the number of Dbvisit Standby trace files to keep. Trace files are generated every time Dbvisit Standby is executed. Trace files are only used for Dbvisit support. Dbvisit Standby will delete trace files greater than this number. Deletes oldest trace file first. Works in conjunction with DAYS_TO_KEEP_TRACE.Least restrictive setting applies between DAYS_TO_KEEP_TRACE and NUM_TRACE_TO_KEEPTo turn off, set to 0.Example:NUM_TRACE_TO_KEEP=100REMOVE_TEMP_FILESDetermines if Dbvisit
2025-04-15Parameter ensures that Dbvisit Standby can identify the archive log name.Default value: archExample: ARCHLOG_PREFIX=archCP_OPTIONSAllow for different secure copy (SCP) options.For example (Unix/Linux): -l limitThe above example "Limits" the used bandwidth, specified in Kbit/sSee man scp in Unix and Linux for SCP options.Example:CP_OPTIONS=-l 100DAYS_TO_KEEP_TRACESpecifies the number of days to keep Dbvisit Standby trace files. Trace files are generated every time Dbvisit Standby is executed.Trace files are only used for Dbvisit Standby support. Dbvisit Standby will delete trace files that are older than this variable value (in days).Works in conjunction with NUM_TRACE_TO_KEEP.Least restrictive setting applies between DAYS_TO_KEEP_TRACE and NUM_TRACE_TO_KEEPTo turn off, set to 0.Example:DAYS_TO_KEEP_TRACE=3DB_CONNECTION_MODEDetermines the type of SQLPLUS connection Dbvisit Standby makes to the database on the primary server.Possible Values:dedicatedDbvisit Standby connects with the dedicated connection mode. The dedicated connection mode initiates a database connection each time information is requested from the database. The connection is closed after each request.shared (Recommended)By default a database connection is opened once at the start of Dbvisit Standby. This connection is used (shared) for all information requested from the database. At the end of Dbvisit Standby processing, the connection is closed.Example:DB_CONNECTION_MODE = dedicatedDB_CONNECTION_MODE_DRDetermines the type of SQLPLUS connection Dbvisit Standby makes to the database on the standby server.Possible Values:dedicatedDbvisit Standby connects with the dedicated connection mode. The dedicated connection mode initiates a database connection each time information is requested from the database. The connection is closed after each request.shared (Recommended)By default a database connection is opened once at the start of Dbvisit Standby. This connection is
2025-03-31