Extra settings
These settings are not present in the DDC file but can be added if required.
Variable Name | Meaning |
---|---|
DBV_PRE_PROC | The name of the pre-processing script. If a different named script should be called, then this variable can be set. If no path name is given the Dbvisit Standby install directory is assumed. |
Default value Windows: dbv_pre_processing.cmd | |
Default value Non Windows: dbv_pre_processing.sh | |
See the | |
Pre- and post-processing section for more information. | |
Example: | |
DBV_PRE_PROC = rman_backup.cmd | |
DBV_POST_PROC | If a different named script should be called, then this variable can be set. If no path name is given the Dbvisit Standby install directory is assumed. |
Default value Windows: dbv_post_processing.cmd | |
Default value Non Windows: dbv_post_processing.sh | |
See the | |
Pre- and post-processing section for more information. | |
Example: | |
DBV_POST_PROC = post_procs_all.cmd | |
WIN_SERVICE_WAIT | How long in seconds to wait for the Windows Oracle service to start or stop before starting or stopping the database. |
Default value: 10 | |
Example: | |
WIN_SERVICE_WAIT=10 | |
AMM_PERC_FULL_WAIT_MILLISEC | This is used in the Archive Management Module (AMM) to ensure that the percentage full disk space displays the correct value. For some volume managers it takes a little time to display the correct status after files have been removed. This variables ensures there is some delay before Dbvisit Standby calculates the free space again. |
This setting is only used in conjunction with the THRESHOLD_ARCHSOURCE and THRESHOLD_ARCHDEST variables. | |
Default is 250 milliseconds. | |
Example: | |
AMM_PERC_FULL_WAIT_MILLISEC=250 | |
AMM_START_AFTER_EACH_APPLY | Use with caution! Archives may be deleted before being applied. |
AMM_START_AFTER_EACH_TRANSFER | Normally the Archive Management Module (AMM) to manage the archive log files is started at the end of Dbvisit Standby processing. These variables allow the AMM module to be started during Dbvisit Standby processing. This may be necessary due to space restrictions. |
AMM_START_AFTER_EACH_APPLY starts AMM on the standby server after each archive has been applied and not at the end of Dbvisit Standby processing. | |
AMM_START_AFTER_EACH_TRANSFER starts AMM on the primary server after each archive has been transferred and not at the end of Dbvisit Standby processing. | |
Important: Normally Dbvisit Standby will apply the archives to the standby database before removing them. By setting AMM_START_AFTER_EACH_TRANSFER=Yes, this check no longer applies. | |
Sample: | |
AMM_START_AFTER_EACH_APPLY=Yes | |
AMM_START_AFTER_EACH_TRANSFER=No | |
ORACLE_SID_ASM | The ASM instance name and the ORACLE_HOME for the ASM instance name. |
ORACLE_HOME_ASM | Default: ORACLE_SID_ASM = +ASM |
SSH_SKIP_OUTPUT | If the ssh connection contains an ssh banner, then Dbvisit Standby will not be able to interpret the data correctly. This setting can be used to tell Dbvisit Standby to ignore the ssh banner. For example if the ssh banner is as follows: *************************************************************************** It is for authorized use only. Users (authorized or unauthorized) Then the following can be set to ignore this: SSH_SKIP_OUTPUT=*** This will skip the output lines beginning with *** and ending with *** |
SSH_SKIP_OUTPUT_LINES
| By setting this parameter to a number value, that number of lines will be ignored during ssh connections. |