The RMS heartbeat feature uses the stored procedure rs_ticket to generate latency information, which is the amount of time it takes for a transaction to move from the primary database to the replicate database. You can use this information to monitor Replication Server performance, module heartbeat, replication health, and table-level quiesce.
At a specified interval, RMS executes rs_ticket at the primary database. The generated latency information is stored in a table in the replicate database. You can use RMS to set up the heartbeat process to retrieve the latency information from the replicate database.
For more information about rs_ticket and its functionality, see Chapter 6, “Adaptive Server Stored Procedures,” in the Replication Server Reference Manual.
RMS API commands to monitor heartbeat are:
get heartbeat – retrieves a list of the heartbeat processes that have been defined in the RMS.
get heartbeat ticket – retrieves a set of tickets from the rms_ticket_history table, for the heartbeat process and date and time range specified.
start heartbeat – sets up and starts a heartbeat process from a specified primary connection to a specified replicate connection.
stop heartbeat – stops the heartbeat process between the primary and replicate databases. Optionally truncates the rms_ticket_history table.
For detailed information about these APIs, see Chapter 9, “Replication Monitoring Services API,” in the Replication Server Reference Manual.
