Table 20. Event status updates in Netcool/OMNIbus are not forwarded to Tivoli Monitoring
Possible cause Resolution Log files to check
Verify the
bi-directional
architecture is
configured.
Verify that the $EVENT_SYNC_INSTALLDIR/
omnibus/itm_sync.sql file was loaded into
the Netcool/OMNIbus ObjectServer, where
$EVENT_SYNC_INSTALLDIR is the
directory where the ITM event
synchronization component was installed.
Use Netcool/OMNIbus Administrator to
verify that triggers from this file are defined
in the ObjectServer. For example, the
itm_event_send and synchronizeitm triggers
should exist.
If the triggers from itm_sync.sql are not
defined in the ObjectServer, see the topic
“Updating the OMNIbus database schema”
in the IBM Tivoli Monitoring Installation and
Setup Guide for the procedure to follow to
add the triggers to the Object Server.
Not applicable.
The IBM Tivoli
Monitoring
Situation Update
Forwarder is not
running on the
computer system
where
Netcool/OMNIbus
ObjectServer is
installed.
Run $EVENT_SYNC_INSTALLDIR/bin/
query_state.sh (UNIX) or
query_state.cmd(Windows) to verify the
Situation Update Forwarder is running. If it
is not running, start it with
$EVENT_SYNC_INSTALLDIR/bin/startSUF.sh
(UNIX) or startSUF.cmd (Windows)
$EVENT_SYNC_INSTALLDIR is the
directory where the IBM Tivoli Monitoring
event synchronization component was
installed.
Look for Situation
Update Forwarder
startup errors in
/tmp/itmsynch/logs/
synch_trace.log.
236 IBM Tivoli Monitoring: Troubleshooting Guide
To Next Page
Loading...
Need help?
General
