Advanced Settings

MAILSUBJECT_PREFIX_LOG_GAP_REPORT

MAILSUBJECT_PREFIX_SUCCESSFUL

MAILSUBJECT_PREFIX_HEARTBEAT

These variables can be used to set a prefix for the email subject line. This can then be used to set filtering rules for emails.

MAILSUBJECT_PREFIX_LOG_GAP_REPORT is for the archive log gap report.

MAILSUBJECT_PREFIX_SUCCESSFUL is for the Dbvisit Standby success email.

MAILSUBJECT_PREFIX_HEARTBEAT is for the Dbvisit Standby heartbeat email.

For example by setting MAILSUBJECT_PREFIX_LOG_GAP_REPORT = 53

The result will be:

"53 - Dbvisit report for PRODB: Transfer log gap: 0 Archive log gap: 0"

MAILCFG_ATTACH_TRACEFILE is to specify whether to attach trace files to error emails so that these can be forwarded to Dbvisit Standby support.

Example :

MAILCFG_ATTACH_TRACEFILE = No

MAILCFG_SENDMAIL_CLIENT is to specify another sendmail client. Full path must be provided.

Example:

MAILCFG_SENDMAIL_CLIENT =C:\\programs\\sendmail.exe

MAILCFG_PORT is to specify another smtp port.

Example:

MAILCFG_PORT = 26

MAILCFG_DEBUG is to turn on smtp debug messages.

Example:

MAILCFG_DEBUG = 1

MAILCFG_TIME_OUT is the specify smtp timeout. 

Example:

MAILCFG_TIME_OUT = 5

SWITCHOVER_TIMEOUT_IN_SEC is the maximum time in seconds that Dbvisit Standby will wait for response from the other server during graceful switchover ONLY.

Default value:

SWITCHOVER_TIMEOUT_IN_SEC = 1500

Example:

SWITCHOVER_TIMEOUT_IN_SEC = 3000

SWITCHOVER_WAIT_IN_SEC is the time interval in seconds between Dbvisit Standby polling the other server for a response during graceful switchover ONLY.

Default value:

SWITCHOVER_WAIT_IN_SEC = 5

Example:

SWITCHOVER_WAIT_IN_SEC = 10

Dbvisit Standby uses short names for the primary and standby servers set by SOURCE and DESTINATION respectively. To use fully qualified domain names for the SOURCE and DESTINATION settings set to Y:

Default:

USE_LONG_SERVER_NAMES = N

Example:

USE_LONG_SERVER_NAMES = Yes

Specifies if tempfiles should be dropped on the standby database after successful completion of Graceful Switchover for Oracle versions 11.2 or higher. This is a workaround to fix Oracle bug 10292173.

Default :

DROP_STANDBY_TEMPFILES = Yes

May take values PARALLEL to enforce parallel recovery of database, or NOPARALLEL to enforce serial recovery of database. If not specified then reset to NOPARALLEL for databases version 11.1 and higher.Defaults to none

Example:

RECOVERY_PARALLELISM = PARALLEL

Set to Y if your environment does not allow for creating a filesystem standby database for an ASM primary database on a standby server that does not have an ASM instance running.

Default:

CSD_FORCE_ASM_REDO_CONVERT = N

Specifies if windows service should be shut down when the standby database is shutdown during creating of standby database and Graceful Switchover

Default:

SHUT_WIN_SERVICE = N

Dbvisit AMM module checks if an archive log has been transferred to standby server(s) before deleteing it.

Default:   

AMM_CHECK_TRANSFERRED = Y

Dbvisit AMM module processes multiple archive destinations when deleting logs on the primary server. Set to N to turn off.

Default:

AMM_PROCESS_MULTIPLE_ARCH_DEST = Y

For multiple standby databases, Dbvisit AMM module checks if an archive log has been transferred to a standby server before deleteing it, if Dbvisit Standby has run at least once within the last DBV_LAST_RUN_OFFSET days

Default:

DBV_LAST_RUN_OFFSET = 1

Number of archive logs Dbvisit AMM module keeps on the server when deleting logs, regardless of AMM settings

Default

MIN_ARCH_TO_KEEP = 3

Automatically run dbvisit -i on the primary server every time Dbvisit executes. dbvisit -i collects the archive and transfer log gap information from the standby database and saves this information for reporting purposes. It will also alert if ARCHIVE_LOG_GAP_THRESHOLD or TRANSFER_LOG_GAP_THRESHOLD have exceeded their threshold.

Default:

RUN_INSPECT = Yes

RMAN_DBF_BACKUP_TYPE

The CSD process is 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 BACKUPSET
RMAN_DBF_BACKUP_TYPE=AS COMPRESSED BACKUPSET
RMAN_DBF_BACKUP_TYPE=AS COPY