Connection Manager event alarm IDs
The class ID for event alarms indicates the type of event. The event ID indicates the specific event.
The following table lists event alarm IDs and messages for the Connection Manager.
You can set your alarm program script to capture the Connection Manager class ID and message and initiate corrective actions or notifications.
You can use the values set in the INFORMIXCMNAME and INFORMIXCMCONUNITNAME environment variables when writing an alarm handler for the Connection Manager. If the Connection Manager raises an event alarm, the Connection Manager instance name is stored in the INFORMIXCMNAME environment variable, and the Connection Manager connection unit name is stored in the INFORMIXCMCONUNITNAME environment variable.
Event alarm messages are written to the Connection Manager log file.
| ID | Severity | Messages | Explanation |
|---|---|---|---|
| Class ID: 1 Event ID: 1001 |
3 | Class message: Connection Manager generic alarm Specific message: Connection Manager stopped |
The Connection Manager stopped running. Online log message: Connection Manager shut down successfully. User action: Restart the Connection Manager, if necessary. |
| Class ID: 1 Event ID: 1002 |
3 | Class message: Connection Manager generic alarm Specific message: Connection Manager fatal error |
The Connection Manager failed to initialize. Online log message: Failed to switch to daemon mode, Connection Manager stopped. Error: Initialize failed, Connection Manager stopped. Error: SLA listener failed, Connection Manager can not start. User action: Check the message file for failure details. Correct any errors and then restart the Connection Manager. |
| Class ID: 1 Event ID: 1003 |
3 | Class message: Connection Manager generic alarm Specific message: Connection Manager received signal |
The Connection Manager stopped or crashed. Online log message: Connection Manager process received signal, shutting down User action: If the Connection Manager was killed by signal 9, no action is required. Otherwise, report the problem to the System Administrator. |
| Class ID: 2 Event ID: 2001 |
3 | Class message: Failover Arbitrator alarm Specific message: Failover in progress |
The Connection Manager Failover Arbitrator
initiated a failover event. Online log message: Failover Arbitrator automated failover in progress. |
| Class ID: 2 Event ID: 2002 |
3 | Class message: Failover Arbitrator alarm Specific message: Failover completed |
The Connection Manager Failover Arbitrator
has completed failover. Online log message: Failover Arbitrator automated failover completed. |
| Class ID: 2 Event ID: 2003 |
3 | Class message: Failover Arbitrator alarm Specific message: Failover disabled |
Automated failover for the Connection Manager
is disabled. Online log message: Failover Arbitrator automated failover is disabled. User action: N/A |
| Class ID: 2 Event ID: 2004 |
3 | Class message: Failover Arbitrator alarm Specific message: Failover Arbitrator aborting automated failover |
Failover processing has failed. Online log message: Failover Arbitrator aborting automated failover. User action: Check the message log file, and then manually start the primary server or manually perform failover. |
| Class ID: 2 Event ID: 2005 |
3 | Class message: Failover Arbitrator alarm Specific message: Failover processing is in manual mode |
Failover processing is not in automatic
mode. Online log message: Failover processing is in manual mode |
| Class ID: 3 Event ID: 3001 |
3 | Class message: Connection to the primary Specific message: Cannot connect to primary server |
The Connection Manager cannot connect to
the primary server. Online log message: Unable to connect to Informix® server. User action: Correct the setup problem. Connection Manager can then connect to the server automatically. |
| Class ID: 3 Event ID: 3002 |
3 | Class message: Connection to the primary Specific message: Lost connection to primary server |
The Connection Manager is disconnected from
the primary server. Online log message: Detected lost connection to Informix server. User action: Correct the setup or network problem. The Connection Manager can then connect to the primary server automatically. |
| Class ID: 3 Event ID: 3003 |
4 | Class message: Connection to the primary Specific message: CM detected multiple primary servers in the cluster |
Connection Manager is connected to multiple primary servers. Online log message: Detected multiple primary servers in the cluster. User action: Correct the setup or network problem so that Connection Manager is connected to only one primary server. |
| Class ID: 4 Event ID: 4001 |
3 | Class message: Connection to ER node Specific message: Cannot connect to ER node |
The Connection Manager cannot connect to
an Enterprise Replication server. User action: Correct the setup problem. The Connection Manager can then connect to the Enterprise Replication server automatically. |
| Class ID: 4 Event ID: 4002 |
3 | Class message: Connection to ER node Specific message: Lost connection to ER node |
The Connection Manager has disconnected
from an Enterprise Replication server. Online log message: Detected lost connection to Informix server User action: Correct the setup or network problem. The Connection Manager can then connect to the Enterprise Replication server automatically. |
| Class ID: 5 Event ID: 5001 |
3 | Class message: Connection to generic server Specific message: Cannot connect to server |
The Connection Manager cannot connect to
a server in a high-availability cluster. Online log message: Unable to connect to Informix server. User action: Correct the setup problem. Connection Manager can then connect to the high-availability server automatically. |
| Class ID: 5 Event ID: 5002 |
3 | Class message: Connection to generic server Specific message: Lost connection to server |
The Connection Manager is disconnected from
a secondary server. Online log message: Detected lost connection to Informix server. User action: Correct the setup or network problem. Connection Manager can then connect to the secondary server automatically. |