get heartbeat tickets

Retrieves a set of tickets from the rms_ticket_history table for the heartbeat process and date and time range specified. The ticket output includes a set of date and time fields for each step in the replication process. The date and time are synchronized to the replicate data server system time.

Syntax

get heartbeat tickets from pds.pdb to rds.rdb
	[start date time] 
	[end date time]
	[last num_tickets]

Parameters

pds.pdb – The name of the primary data server and database.
rds.rdb – The name of the replicate data server and database.
start date time – The starting date and time for the range of tickets. The RMS retrieves ticket information starting with this time and ending at either the end time, or the end of the table. If you do not provide this parameter, the RMS starts at the oldest ticket in the table.
end date time – The ending date and time for the range of tickets. The RMS retrieves ticket information starting at the specified time until this time. If you do not provide this parameter, the RMS includes all tickets starting with the start time.
last num_tickets – Retrieves the specified number of tickets from the table. You cannot use this parameter with the start and end parameters

Examples

Example 1 – Retrieves all rows from the rms_ticket_history table:

get heartbeat tickets
    from inventory_pds.vendor to inventory_dss.vendor

Example 2 – Retrieves all rows between Oct 29th and November 3rd:

get heartbeat tickets 
    from inventory_pds.vendor to inventory_dss.vendor
    start Oct 29, 2005 12:00am
    end Nov 3, 2005 12:00am

Example 3 – Retrieves all rows in the table starting at October 29th at 1:30:

get heartbeat tickets
    from inventory_pds.vendor to inventory_dss.vendor
    start 10/29 1:30pm

Example 4 – Retrieves the 500 latest rows in the table:

get heartbeat tickets
    from inventory_pds.vendor to inventory_dss.vendor
    last 500

Usage

The start and end parameters support multiple date and time formats; for example, you can enter the date in the format MM/DD/YYYY (such as 10/29/2005), or in the format MMM DD, YYYY (such as Oct 29, 2005). The time fields support an entry without seconds or milliseconds, as well as localized date and time formats.
All dates in the result set are synchronized to the replicate data server system time. Before the result set is generated, the RMS retrieves the date and time from the data servers and Replication Servers, and adjusts the time by the difference between the server’s time and the RMS system’s time.

The get heartbeat tickets command returns the following result set:

Column Descriptions for get heartbeat tickets
Column	Type	Description
`Primary`	`varchar`	The name of the primary data server and database.
`Replicate`	`varchar`	The name of the replicate data server and database.
`PDB`	`datetime`	The time that the rs_ticket stored procedure was executed at the primary database.
`EXEC`	`datetime`	The time the ticket passed through the primary Replication Server executor thread.
`Bytes`	`int`	Total bytes the executor thread received from the RepAgent or Replication Agent.
`DIST`	`datetime`	The time the ticket passed through the primary Replication Server distributor thread.
`DSI`	`datetime`	The time the ticket passed through the replicate Replication Server DSI thread.
`RDB`	`datetime`	The time the ticket arrived at the replicate data server. The result set is sorted by the RDB field.