If run on the coordinator node, displays INC heartbeat status for every node. If executed on a secondary node, displays INC heartbeat status for just the current node.
Multiplex only.
You must have EXECUTE privilege on the system procedure, as well as the MANAGE MULTIPLEX system privilege.
The sp_iqmpxincheartbeatinfo procedure returns:
| Column Name | Data Type | Description | Values |
|---|---|---|---|
| server_id | unsigned int | Identifier for the server | |
| server_name | char(128) | Name of the server | |
| last_positive_hb | TIMESTAMP | Date/time of last successful heartbeat ping | DD:MM:YYYY:HH:MM:SS |
| time_not_responding | TIME | Time since last successful heartbeat ping | HH:MM:SS |
| time_until_timeout | TIME | If a node is not responding, the time left until node is declared offline. |
Sample output of sp_iqmpxincheartbeatinfo.
server_id,server_name,last_positive_hb, time_not_responding,time_until_timeout 2,'r2_dbsrv90210',2012-11-17 15:48:42.0,00:00:00,00:00:00 3,'w3_dbsrv90210',2012-11-17 15:48:42.0,00:00:00,00:00:00
If the elapsed time exceeds 24 hours, SAP Sybase IQ returns sp_iqmpxincheartbeatinfo output like the following:
server_id,server_name,last_positive_hb, time_not_responding,time_until_timeout 2,'r2_mpx_cr_srv',Jan 14 2013 11:57AM,11:59PM,11:59PM 3,'w4_mpx_cr_srv',Jan 14 2013 11:57AM,11:59PM,11:59PM (2 rows affected) (return status = 0)
A value of 11:59PM in the time_not_responding and time_until_timeout columns means that the time has crossed the 24-hour limit.