1. Alarms and KPIs Guide
  2. Alarms and Events
  3. Communication Agent, ComAgent (19420-19909)
  4. 19860 - Communication Agent Configuration Daemon Table Monitoring Failure

3.7.47 19860 - Communication Agent Configuration Daemon Table Monitoring Failure

Alarm Group:
CAF
Description:
This alarm indicates that a Communication Agent Configuration Daemon has encountered an error that prevents it from properly using server topology configuration data to configure automatic connections for the Communication Agents on MPs, and this may prevent applications on MPs from communicating.
Severity:
Critical
Instance:
None
HA Score:
Normal
Auto Clear Seconds:
0 (zero)
OID:
CAFTableMonitorFailureNotify
Cause:
Alarm 19860 is asserted when Communication Agent Configuration Daemon is unable to monitor one or more tables that it has been configured to monitor.
Diagnostic Information:
This alarm indicates that a Communication Agent Configuration Daemon has encountered an error that prevents it from properly using server topology configuration data to configure automatic connections for the Communication Agents on MPs, and this may prevent applications on MPs from communicating.
To troubleshoot:
  • Find additional information for the alarm in Alarms & Events, and then View History by locating the row with a sequence number that matches the active alarm sequence number and viewing the Additional Info column.
  • Check the event history logs at Alarms & Events, and then View History for additional Communication Agent events or alarms from this server.

Recovery:

  1. Use Alarms & Events, and then View History to find additional information about the alarm.

    The information can be found by locating the row with a sequence number that matches the active alarm sequence number and viewing the Additional Info column.

  2. Check the event history logs at Alarms & Events, and then View History for additional Communication Agent events or alarms from this MP server.
  3. If conditions do not permit a forced failover of the active NOAM, it is recommended to contact My Oracle Support for assistance.
  4. If conditions permit, then initiate a failover of active NOAM.
    This causes the Communication Agent Configuration Daemon to exit on the originally-active NOAM and to start on the newly-active NOAM.
  5. After NOAM failover completes, verify the alarm has cleared.
  6. If the alarm has not cleared, it is recommended to contact My Oracle Support for assistance.