Dbvisit standby
Author: E | 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
Installing Dbvisit Standby - Dbvisit Standby 8.0 User Guide - Dbvisit
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 DbvisitDbvisit Standby License - Dbvisit Standby 10.0 User Guide - Dbvisit
Disable the run of "dbvisit -i" command at the beginning of each Dbvisit Standby execution on the primary server.This can improve the execution time of Dbvisit Standby on the primary server, but there will be no reporting information available in the Dbvisit Standby repository.The default value is YExample: RUN_INSPECT = YSEND_HEARTBEAT_TIME24This variable will indicate the time of the day the Heartbeat (Email) will be sent.The Heartbeat is a daily email to Dbvisit Standby is active. This will be sent from the primary and standby server.The time is in 24-hour format and should be between 0000 and 2359 and must be 4 digits. If this variable is not present, an email will be sent at the start of each day (midnight).Multiple times separated by comma can be set. It is recommended that you also review the E-Mail setup variables.Example:SEND_HEARTBEAT_TIME24 = 0700Example with multiple times specified:SEND_HEARTBEAT_TIME24 = 0700:1300:1800SERVICE_USEDThe variable has the default value of N.If there are any services in the database running the value has to be set to Y by editing the DDC either by using the GUI console or by using a text editorThis will result in adding a -f/force flag to the srvctl "stop instance" command to avoid below error.CRS-2529: Unable to act on 'ora.cpms.db' because that would require stopping orrelocating 'ora.cpms.cpmsdb_srv.svc', but the force option was not specifiedExample:If service is used in database check using the below command.oracle@kiwi1[/home/oracle]: srvctl status service -d DEV -s DEVSRVService DEVSRV is running on instance(s) DEV1If you see any service running change. 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 StandbyUpgrade Dbvisit Standby - Dbvisit Standby 8.0 User Guide - Dbvisit
Parameter 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 isUninstalling Dbvisit Standby - User Guide Dbvisit Standby 7.0 - Dbvisit
Used (shared) for all information requested from the database. At the end of Dbvisit Standby processing, the connection is closed.Example:DB_CONNECTION_MODE_DR = dedicatedDBV_LAST_RUN_OFFSETFor multiple standby databases, Dbvisit AMM module checks if an archive log has been transferred to a standby server before deleting it if Dbvisit Standby has run at least once within the last DBV_LAST_RUN_OFFSET daysThe default value is 1DBV_RECOVERY_PARALLELISMMay take values PARALLEL to enforce parallel recovery of the database, or NOPARALLEL to enforce serial recovery of the database.If not specified then reset to NOPARALLEL for databases version 11.1 and higherDefaults to noneExample:DBV_RECOVERY_PARALLELISM = PARALLELHOSTNAME_CMDIf Dbvisit Standby is part of a cluster and a different hostname should be used instead of the regular hostname returned by the current server, then this variable can be used to specify a command to set the hostname for Dbvisit Standby. For example, When Dbvisit Standby is used in a cluster and the virtual cluster name should be used instead of the physical hostname.Example:HOSTNAME_CMD=/usr/local/bin/hostname.shThe above script can then contain the following: #!/bin/bash echo "server1"The name "server1" should be able to resolve to an IP address. In case of a cluster configuration (example Oracle Fail-Safe), this name should resolve to the Cluster IP address.If the HOSTNAME_CMD file is specified but does not exist on the server, then Dbvisit Standby ignores the HOSTNAME_CMD and uses the regular method to obtain the hostname of the server. This is useful if the standby server is a regular server and the default hostname is sufficient.INITIATE_DBVISIT_ON_STANDBYSetting this to Y:Dbvisit Standby whenUpgrade Dbvisit Standby – Dbvisit Support
Once you have created the standby database manually using RMAN, configure Dbvisit Standby to automatically send and apply logs to standby database.1) Install latest Dbvisit Standby software on both primary and standby servers. Please download the latest release (7.0.60) here: refer here for the installation guide: Configure DDC file, AMM, and Database repository by running ./dbvisit_setup executable on primary. Choose option 1 from the menu to configure them.Options: 1) New Dbvisit Database setup (combines options 2,3,4)Ref: done, you should have now a DDC file created on primary that will automatically be transferred to standby server.3) You can then try sending and applying of logs manually to test if everything is running fine. Please refer below link.Ref: Once send and apply of logs are fine, you can then schedule Dbvisit default commands (ship and transfer). You have two options here - either via GUI (if you are running dbvserver GUI) or via cron. Please refer below links for more details.. 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 StandbyComments
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-18Be 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-24Parameter 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-04-09Used (shared) for all information requested from the database. At the end of Dbvisit Standby processing, the connection is closed.Example:DB_CONNECTION_MODE_DR = dedicatedDBV_LAST_RUN_OFFSETFor multiple standby databases, Dbvisit AMM module checks if an archive log has been transferred to a standby server before deleting it if Dbvisit Standby has run at least once within the last DBV_LAST_RUN_OFFSET daysThe default value is 1DBV_RECOVERY_PARALLELISMMay take values PARALLEL to enforce parallel recovery of the database, or NOPARALLEL to enforce serial recovery of the database.If not specified then reset to NOPARALLEL for databases version 11.1 and higherDefaults to noneExample:DBV_RECOVERY_PARALLELISM = PARALLELHOSTNAME_CMDIf Dbvisit Standby is part of a cluster and a different hostname should be used instead of the regular hostname returned by the current server, then this variable can be used to specify a command to set the hostname for Dbvisit Standby. For example, When Dbvisit Standby is used in a cluster and the virtual cluster name should be used instead of the physical hostname.Example:HOSTNAME_CMD=/usr/local/bin/hostname.shThe above script can then contain the following: #!/bin/bash echo "server1"The name "server1" should be able to resolve to an IP address. In case of a cluster configuration (example Oracle Fail-Safe), this name should resolve to the Cluster IP address.If the HOSTNAME_CMD file is specified but does not exist on the server, then Dbvisit Standby ignores the HOSTNAME_CMD and uses the regular method to obtain the hostname of the server. This is useful if the standby server is a regular server and the default hostname is sufficient.INITIATE_DBVISIT_ON_STANDBYSetting this to Y:Dbvisit Standby when
2025-04-23Standby temporary files should be deleted after Dbvisit Standby processing. Possible Values:Y (Default Value)Dbvisit Standby temporary files will be deleted. NDbvisit Standby temporary files will NOT be deleted.Example: REMOVE_TEMP_FILES=YRETRIES_WAIT_IN_SECTime in seconds to wait before performing another transfer if a previous transfer failed.Default value: 5Example: RETRIES_WAIT_IN_SEC=10Time in seconds to wait before performing another transfer if a previous transfer failed.Default value: 5Example: RETRIES_WAIT_IN_SEC=10RMAN_DBF_BACKUP_TYPEThe CSD process is by default making use of RMAN (when direct transfer is not used). To be more specific COMPRESSED BACKUPSET is used for the backups. In certain scenarios it might be required to adjust the backup option to not use compressed backups or to rather use image copies. This can be done by setting the RMAN_DBF_BACKUP_TYPE parameter in the primary server DDC file. This parameter can be set to specify if a backupset, compressed backupset or image copies are to be used during the CSD operation:Valid options are:RMAN_DBF_BACKUP_TYPE=AS BACKUPSETRMAN_DBF_BACKUP_TYPE=AS COMPRESSED BACKUPSETRMAN_DBF_BACKUP_TYPE=AS COPYRSH_OPTIONSAllow for different secure shell (ssh) options.For example (Unix/Linux): -l login_nameSpecifies the user to log in as on the remote machine. See man ssh in Unix and Linux for ssh options.See sexec on Windows for ssh options.Example:RSH_OPTIONS=-l oracle2RUN_INSPECTIf this value is set (default is yes) Dbvisit Standby will Automatically run "dbvisit -i" command on the primary server every time Dbvisit executes.The command "dbvisit -i" collects the archive and transfer log gap information from the standby database and saves this information for reporting purposes in the Dbvisit Standby repository.This parameter can be set to "N" (No) which will
2025-04-14Started in recovery mode if dbvisit standby is run on the standby to apply logs.APPLY_ARCHIVE_RMANBy default, Dbvisit Standby is making use of SQL commands to perform standby database recovery.The recover command is executed from SQL*Plus and the requested archive log is provided for recovery.When running this in an Oracle RAC environment, where the standby database will need to recover using multiple threads, the recovery process - especially in busy systems or systems where many archive logs needs to be applied,can take longer than it would, if as an alternative the recovery process is making use of RMAN recovery commands.To enable the use of RMAN recovery commands on the standby database to perform recovery, set APPLY_ARCHIVE_RMAN=Y in the DDC file.The default value is APPLY_ARCHIVE_RMAN=NThis parameter will only have an effect on the standby database.The archive logs will still be shipped to the standby database and located in the Dbvisit Standby ARCHDEST. From here when Dbvisit Standby is executed on the standby database,the archive logs will be catalogued in the controlfile and then applied using RMAN recovery commands. This process does require that the archive logs on the standby be uncompressed in the ARCHDEST, which will require more storage for the ARCHDEST to hold the uncompressed archive logs.Setting APPLY_ARCHIVE_RMAN=Y can be used for non-RAC databases as well.ARCHLOG_PREFIXThe archive log may be renamed by another process or in some cases Oracle prefixes the archive with the word "arch". If this happens, Dbvisit Standby may not be able to identify the archive log.Setting this
2025-04-14