From Dbvisit Standby version 7.0.10 SSL/TLS Email (SMTP) server connectivity is supported.
It is required that the MAILCFG_PROTOCOL parameter is set in the Dbvisit Standby Configuration (DDC) file with possible values SSL or TLS.
Example, if Gmail is used the following values must be manually specified in the primary server DDC file:
MAILCFG_SMTP_SERVER = smtp.gmail.com MAILCFG_AUTH_USER = gmail username (this will also become the "from" address ) MAILCFG_AUTH_PASSWD = gmail password MAILCFG_PORT = 465 MAILCFG_PROTOCOL = SSL |
A heartbeat e-mail will be sent each new day.
The variable SEND_HEARTBEAT_TIME24 in the Dbvisit Database Configuration (DDC) file specifies what time the email will be sent. The time is in 24-hour format and should be between 0000 and 2359 hours. If this variable is not specified then an email will be sent at the beginning of each day.
Example:
SEND_HEARTBEAT_TIME24 = 0700 |
Multiple times can be specified separated by a semicolon. To send a heartbeat message three times a day (7 am, 1 pm and 6 pm) specify:
SEND_HEARTBEAT_TIME24 = 0700:1300:1800 |
Dbvisit will not necessarily send an email at the exact time specified. Dbvisit will only send the heartbeat email when it is executed.
Example: If SEND_HEARTBEAT_TIME24=1400, but Dbvisit is not executed until 14:20, then the heartbeat email will be sent at 14:20.
It is possible to turn the heartbeat feature off for the primary server by setting SEND_HEARTBEAT=N in the Dbvisit Database Configuration (DDC) file.
To turn the heartbeat feature off for the standby server, set SEND_HEARTBEAT_DR=N.
To test the scheduler heartbeat message and to send a test email, following command can be used: "dbvctl -f send_heartbeat -d <ddc>"
Example output of heartbeat message:
Dbvisit Standby process (8.0.14.19191) is running on dbvlin103 on Thu Oct 12 21:54:54 2017 (scheduler check at 0:0 hours). Dbvisit Standby log gap report for DEVCDB thread 1 at 201710122154: ------------------------------------------------------------- Destination database on dbvlin104 is at sequence: 125. Source database on dbvlin103 is at log sequence: 127. Source database on dbvlin103 is at archived log sequence: 126. Dbvisit Standby last transfer log sequence: 126. Dbvisit Standby last transfer at: 2017-10-12 21:54:41. Archive log gap for DEVCDB: 1. Transfer log gap for DEVCDB: 0. Standby database time lag (DAYS-HH:MI:SS): +00:06:48. |
5. The Log Gap Report And Heartbeat Message
As part of the Daily scheduler heartbeat message, it is possible to include the Dbvisit Standby log gap report.
The Dbvisit Standby log gap reports on the:
To include the Dbvisit Standby archive and transfer log gap report in the daily heartbeat message set:
SEND_LOG_GAP_WITH_HEARTBEAT=Y |
Dbvisit Standby will start the standby database if the standby database is not running and AUTO_START_STANDBY_DB = Y |
There are two modes for emailing on the primary server and they are controlled with the SUCCESSMAIL parameter which can take one of two possible values, Y for yes or N for no.
SUCCESSMAIL=Y|N |
There are two modes for emailing on the standby server and they are controlled with the SUCCESSMAIL_DR parameter which can take one of two possible values, Y for yes or N for no.
SUCCESSMAIL_DR=Y|N |
The email addresses are specified by the ADMINS and SUCCESS_MAILTO parameters in the DDC file. Multiple email addresses can be separated by a comma.
All email configurations are specified in the Dbvisit Standby Database Configuration (DDC) file located in DBVISIT_BASE/standby/conf directory.
If SUCCESS_MAILTO is not set, all emails notifications that Dbvisit Standby sends go to ADMINS.
If SUCCESS_MAILTO is set to a valid email address and SUCCESSMAIL is set to Y then:
- And the following messages go to SUCCESS_MAILTO:
If SUCCESS_MAILTO is set to a valid email address but SUCCESSMAIL is set to N then the following type of messages will not be sent at all: