Measures reported by IBMDB2RepHrtBtTest

A ‘heartbeat” is a signal sent between a primary database and standby database. This signal is taken as a sign of vitality. If there is no response to the signal, then it is understood that there are certain health issues/ technical problems with the primary database.

If the standby database does not receive any heartbeats from a primary database for a certain timeout period, then a ‘Heartbeat Lost” condition occurs and the corresponding standby database is deemed to be dead/unavailable.

To avoid the loss of heartbeats and the consequent failure of a standby database, administrators must keep a close watch on the heartbeats sent by the primary database to each standby database, detect issues in the transmission of heartbeats, and clear the bottlenecks well before the configured timeout period expires and the standby database is declared dead. This can be achieved using the IBMDB2RepHrtBtTest!

This test monitors the heartbeats that each DB2 UDB primary database sends to the standby database. In the process, the test reports the count of heartbeats that were missed during a measure period, the count of heartbeats expected during a measure period and the percentage of heartbeats missed between the primary and standby database. Alerts are promptly sent out if too many heartbeats are missed. This way, administrators can proactively detect problems in heartbeat communication and can resolve them before the standby databases die.

Outputs of the test : One set of results for each database created on the target database server instance being monitored

The measures made by this test are as follows: