Advanced Settings

Variable Name	Meaning

Variable Name	Meaning
SUCCESS_MAILTO	This is used to separate the success emails from the failure emails. If set, then all successful Dbvisit Standby emails will be sent to this email address. Failure or unsuccessful emails will be sent to the email address specified by ADMINS. If not set, then all emails will go to ADMINS.
	Example:
	SUCCESS_MAILTO=success@mycompany.com
DB_CONNECTION_MODE	Determines the type of connection Dbvisit Standby makes to the database on the primary server.
	Values are dedicated or shared.
	Dedicated is the default.
	- Dedicated
	By default Dbvisit 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
	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.
	If the time taken to establish a database connection is too long, Dbvisit Standby may be optimised to improve performance by setting DB_CONNECTION_MODE = shared. The connection to the database is then only made once.
	If you are not sure set to dedicated.
	Example:
	DB_CONNECTION_MODE = shared
DB_CONNECTION_MODE_DR	Determines the type of connection Dbvisit Standby makes to the database on the standby server.
	Values are dedicated or shared.
	Dedicated is the default.
	- Dedicated
	By default Dbvisit 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
	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.
	If the time taken to establish a database connection is too long, Dbvisit Standby may be optimised to improve performance by setting DB_CONNECTION_MODE_DR = shared. The connection to the database is then only made once.
	If you are not sure set to dedicated.
	Example:
	DB_CONNECTION_MODE_DR = shared
IGNORE_ARCH_HIST	Default value: No
	Possible values: Yes, No
	Yes = Use Dbvisit Standby own internal mechanism to find the next available log to transfer.
	No = Use Oracle controlfile information to find the next available log file. If this information is no longer available in the controlfile, default to using Dbvisit Standby’s own internal mechanism.
	If you are not sure, set to No.
	During initial Dbvisit Standby testing, setting this to Yes is useful, as the archive log file to transfer to the standby database is not always easily available in Oracle, especially if there has been a network outage and the standby database has not been updated for a while.
	Example:
	IGNORE_ARCH_HIST=No
USE_STORE_ARCH_SEQ	Graceful Switchover only
	Set to Yes if during initial Graceful Switchover testing Oracle cannot find new archives to recover database.
	Possible values: No, Yes
	Example:
	USE_STORE_ARCH_SEQ=No
FLASH_ARCH_DIRNAME	Name of the directory used by Oracle for flash_recovery area for archive logs.
	Default value: archivelog
	Example:
	FLASH_ARCH_DIRNAME=archivelog
FLASH_DIR_NUM	How many days to go back to look for archive logs in flash recovery area. Each day will have a new directory in the flash recovery area.
	Default value: 40
	Example:
	FLASH_DIR_NUM=40
FLASH_DIR_FORMAT	Format of the archive log directory when using flash recovery area. Standard a directory will be created for every day to hold the archives. This variable dictates the date format of the day directory.
	Default value: YYYY_MM_DD
	Example:
	FLASH_DIR_FORMAT=YYYY_MM_DD
FORCE_FLASH_AREA	Force the use of the flash_area or DB_RECOVERY_FILE area. Only necessary when Dbvisit Standby does not recognize a flash area is in use.
	Yes = Force flash area.
	No = Let Dbvisit Standby determine to use flash area or not.
	Ignore = Ignore flash area when Dbvisit Standby has detected flash area.
	Example:
	FORCE_FLASH_AREA=No
FLASH_ARCHIVE_LOG_FORMAT	Default log_archive_format for when flash area is being used.
	The log_archive_format specified in v$parameter is ignored and a default is being used. This parameter allows tuning off the default parameter when Dbvisit Standby is not able to determine the default parameter.
	Default value: *_%t_%s_%r.arc
	Example:
	FLASH_ARCHIVE_LOG_FORMAT=*_%t_%s_%r.arc
ARCHLOG_PREFIX	The 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 parameter ensures that Dbvisit Standby can identify the archive log name.
	Default value: arch
	Example:
	ARCHLOG_PREFIX=arch
RESYNCH_SEQ_OFFSET	This determines the archive log sequence offset when Dbvisit Standby resynchs with the standby database. A value of 1, means the standby sequence will be offset with -1 and the first sequence is resent.
	Default value: 1
	Example:
	RESYNCH_SEQ_OFFSET=1
ALERT_ON_WARNING	Normally Dbvisit Standby will only alert on errors and then stop processing. Dbvisit Standby will not alert on warnings.
	Possible values: No, Yes
	Yes = Dbvisit Standby will alert on warnings and stop processing.
	No = Dbvisit Standby will alert on errors only and stop processing. Warnings will be displayed in the Dbvisit Standby log file.
	Default value: No
	Example:
	ALERT_ON_WARNING = No
IGNORE_RESETLOG_ID	Ignore the %r parameter in the log_archive_format. This may be used if Dbvisit Standby fails to recognize the log archive format, or Dbvisit Standby is unable to obtain the Resetlogs Id.
	Possible values: Yes, No
	Default value: No.
	Example:
	IGNORE_RESETLOG_ID = No
THREAD_SOURCE	If set to Yes, the THREAD number from the instance is obtained to determine the next archive to send. This may be set to Yes if Dbvisit Standby fails to recognize the archive log sequence.
	Default value: No
	Possible values: Yes, No
	For RAC this is always set to Yes.
	Example:
	THREAD_SOURCE=No
THREAD_DEST	If set to Yes, the THREAD number from the instance is obtained to determine the next archive to apply. This may be set to Yes if Dbvisit Standby fails to recognize the archive log sequence. For RAC this is always set to Yes.
	Default value: No
	Possible values: Yes, No
	Example:
	THREAD_DEST=No
SHOW_TRACEFILE_NAME	Determines when to show the tracefile name.
	Possible values: Yes, No
	Yes = Will show tracefile name in alerts, errors and success emails.
	No = Will show tracefile name in alerts and errors.
	Default value: No
	Example:
	SHOW_TRACEFILE_NAME=No
SHOW_TIME_IN_TRACE	Shows the timestamp in the trace file. There is no significant overhead in displaying the timestamp in the trace file.
	Possible values: Yes, No
	Yes = Will show current timestamp on every line in tracefile.
	No = Will not show timestamp in tracefile.
	Default value: Yes
	Example:
	SHOW_TIME_IN_TRACE=Yes
LOG_SWITCH_WAIT_IN_SEC	Wait 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: 3
	Example:
	LOG_SWITCH_WAIT_IN_SEC=3
LD_LIBRARY_PATH	Sets the library path. This is needed for some versions of Oracle. Not needed for Windows. Do not include the ORACLE_HOME in the path. This will be done automatically.
	Default value: none
	Example:
	LD_LIBRARY_PATH=/usr/dt/lib;/usr/openwin/lib
FORCE_SYSDBA	Determines how Dbvisit Standby will connect to the database to perform its actions.
	Possible values: Yes, No
	Yes = Dbvisit Standby will connect as sysdba. The DBUSER schema will not be used to connect to the database,
	No = Dbvisit Standby will connect with Dbvisit Standby database repository (DDR) user.
	Dbvisit Standby will always connect to the database as sysdba to stop and start the database and to get the status of the database. Dbvisit Standby will always connect to the standby database with sysdba.
	Default value: No
	Example:
	FORCE_SYSDBA=No
ALT_ARCH_LOCATION	This may be added if an alternate LOG_ARCHIVE_DEST is required. Standard, Dbvisit Standby uses the Oracle LOG_ARCHIVE_DEST parameters to determine the location of the archive log files.
	If ALT_ARCH_LOCATION is set, then a process must be in place to copy the archive log files from the default LOG_ARCHIVE_DEST to the alternate location, otherwise Dbvisit Standby will not be able to find the archive log files.
	Default value: None
	Example:
	ALT_ARCH_LOCATION=/oracle/oraarch/altlocation/
	ALT_ARCH_LOCATION=c:\oracle\oraarch\altlocation\
SEND_MAIL_FLAG	Description: Determines if Dbvisit Standby will use email for alerting.
SEND_MAIL_FLAG_DR	Default value: Yes
	Possible values: Yes, No
	Yes = Dbvisit Standby will email.
	No = Dbvisit Standby will NOT email.
	SEND_MAIL_FLAG is for both primary server and standby servers.
	SEND_MAIL_FLAG_DR is only for the standby server.
	If SEND_MAIL_FLAG_DR is not set then SEND_MAIL_FLAG will apply to both primary and standby servers.
	Warning: If set to No, Dbvisit Standby will not send any notification when an alert is triggered.
	Default value: Yes
	Example:
	SEND_MAIL_FLAG=Yes
	SEND_MAIL_FLAG_DR=No
SEND_HEARTBEAT	Determines if a daily heart beat message is sent to ensure Dbvisit Standby is still scheduled.
SEND_HEARTBEAT_DR	Possible values: Yes, No
	Yes = Dbvisit Standby sends daily heartbeat email.
	No = Dbvisit Standby will not send daily heartbeat email.
	Warning: If set to No, you must have an alternative method to ensure Dbvisit Standby is processing is active.
	SEND_HEARTBEAT is used for the primary server.
	SEND_HEARTBEAT_DR is used for the standby server.
	Default value: Yes
	Example:
	SEND_HEARTBEAT=Yes
	SEND_HEARTBEAT_DR=No
LOGGING_LEVEL	Determines the level of logging for the Dbvisit Standby log file.
	Default value: all
	The values are:
	all = All messages will be logged.
	important = Only important messages will be logged, the following messages will NOT be logged:
	- Log not found on standby database
	- Dbvisit Standby still running
	- Dbvisit Standby pre-processing completed
	- Dbvisit Standby post-processing completed
	- Schedular heartbeat message sent
	- Duplicate compressed file found
	Example:
	LOGGING_LEVEL = important
ARCH_BUSY	Name of lock file to indicate the archive file is in use.
	Default value: archive_busy.lck
	Example:
	ARCH_BUSY=archive_busy.lck
ARCH_NOT_THERE	Name of file to indicate the archive file is not found.
	Default value: arch_not_there.lck
	Example:
	ARCH_NOT_THERE=arch_not_there.lck
CHECKFOR_PREV_VERSION	Determines if Dbvisit Standby will perform a check if the database configuration file if from a previous Dbvisit Standby version. Once the database configuration file is updated, this can be set to No.
	Possible values: Yes, No
	Yes = Dbvisit Standby checks for previous database configuration files every time Dbvisit Standby is executed.
	No = Dbvisit Standby will not perform the check.
	Default value: Yes
	Example:
	CHECKFOR_PREV_VERSION=Yes
COMPARE_CHECKSUM	Determines if Dbvisit Standby will perform a checksum and compare the checksum on the file that has been transferred. If the checksum is not the same, Dbvisit Standby will alert.
	Possible values: Yes, No
	Yes = Dbvisit Standby will calculate checksum on the file being transferred and will alert if the transferred file is not the same as the original file.
	No = Dbvisit Standby will not perform a checksum. It is not guaranteed that the transferred file will be the same as the original file.
	Default value: Yes
	Example:
	COMPARE_CHECKSUM=Yes
REMOVE_TEMP_FILES	Determines if Dbvisit Standby temporary files should be deleted after Dbvisit Standby processing.
	Possible values: Yes, No
	Yes = Dbvisit Standby temporary files will be deleted.
	No = Dbvisit Standby temporary files will NOT be deleted.
	Default value: Yes
	Example:
	REMOVE_TEMP_FILES=Yes
TRANSFER_RETRIES	Determines the number of retries when the checksum of the transferred log file does not match the original file. When the checksum does not match, the file will be transferred again. If the checksum does not match after TRANSFER_RETRIES attempts, an alert will be raised.
	Default value: 2
	Example:
	TRANSFER_RETRIES=2
SYNCH_ENV_FILE_ONLY	Variable SYNCH_DBVISIT_INSTALL=Yes must be set for this setting to be active.
	Possible values: Yes, No
	No = Complete Dbvisit Standby installation and configuration (DDC) file will be synchronised everytime Dbvisit Standby executes.
	Yes = Only Dbvisit Standby database configurational (DDC) file will be synchronised everytime Dbvisit Standby executes.
	Note: The complete Dbvisit Standby installation can be synchronised with the dbvisit -c <DDC> command.
	Example:
	SYNCH_ENV_FILE_ONLY=Yes
EMAIL_LOG_GAP_REPORT