ProbeWatch messages
During normal operations, the probe generates ProbeWatch messages and sends them to the ObjectServer. These messages tell the ObjectServer how the probe is running.
The following table describes the raw ProbeWatch messages that the probe generates. For information about generic ProbeWatch messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.
ProbeWatch message |
Description |
Triggers/causes |
|---|---|---|
| Exception during marshalling notification message in parser that may cause event loss! | An exception occurred while the probe was creating an Objectserver event from an incoming notification. This can cause loss of events in the probe. |
This message can be caused by an error in any of the services that the probe uses to create the ObjectServer event. To obtain more information about this occurrence, enable data stream capture. This enables you to get a detailed view of the information the probe receives from the OPC UA server. See Data stream capture. |
| Exception during adding notification message into queue and may causing event loss. | An exception occurred while the probe was adding an incoming notification to the queue of messages awaiting processing into ObjectServer events. This can cause event loss in the probe. |
This message can be caused by an error in any of the services that the probe uses to queue incoming notification messages. To obtain more information about this occurrence, refer to the DSL Log file (opc_ua_dsl.log in $NCHOME/omnibus/probes, by default). |
| Unable to parse the incoming DataChangeNotification. | An exception occurred while the probe was processing a data change notification. |
This message can be caused by an error in any of the services that the probe uses to parse data change notifications. To obtain more information about this occurrence, enable data stream capture. This enables you to get a detailed view of the information the probe receives from the OPC UA server. See Data stream capture. |
| Unable to parse the incoming EventListNotification. | An exception occurred while the probe was processing an event list notification. |
This message can be caused by any of the services that the probe uses to parse event list notifications. To obtain more information about this occurrence, enable data stream capture. This enables you to get a detailed view of the information the probe receives from the OPC UA server. See Data stream capture. |
| Unable to parse the incoming StateChangeNotification. | An exception occurred while the probe was processing a state change notification. |
This message can be caused by any of the services that the probe uses to parse state change notifications. To obtain more information about this occurrence, enable data stream capture. This enables you to get a detailed view of the information the probe receives from the OPC UA server. See Data stream capture. |
| Unable to create events in object server. | An exception occurred while the probe was adding an event to a queue ready for transmission to the ObjectServer. This can cause event loss in the probe. |
Contact IBM Support. |
| START SYNCHRONIZATION | The probe has begun a scheduled resynchronization with the OPC UA server. |
This is normal behavior based on the values of the InitialResync and ResyncInterval properties. |
| END SYNCHRONIZATION | A scheduled resynchronization with the OPC UA server is complete. |
The synchronization operation has completed normally. |