IDC Heartbeat:

To ensure that Ignite processes are running properly at all times, system monitoring tools and/or automated scripts on the repository server can be used to check the heartbeat of the Ignite Data Collector (IDC). IDC processes connect to the repository database and are responsible for recording all statistics gathered from the monitored databases (See Figure 1 below). As these processes connect to the repository database, they update a parameter in the CONPRM table, called 'PI_HEARTBEAT'. The value of this parameter can be stored off and checked periodically to ensure that IDC processes are connecting successfully to the repository database and not erroring out for any other reason.

Figure 1.  Ignite Processes

The sql statement to check the health of the IDC processes to the repository database is listed below. This statement should be run from the Ignite Administrator account, on the repository database, at 10 minute intervals, to check that the value of the heartbeat is changing.

select V from CONPRM where P = 'PI_HEARTBEAT';