IJ18064: ITM SITUATION EVENT WITH 'D' STATUS (SITUATION DELETED) MAY CAUSE ERRONEOUS CLOSURE OF EVENTS IN OMNIBUS

IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 3 (6.3.0.7-TIV-ITM-SP0003)

APAR status

• Closed as program error.

Error description

• Environment: Across releases
  
  Approver: MK
  
  
  Problem Description: Un-assigning a management system from a
  situation causes raised events from the same situation
  distributed to agents attached to other RTEMS to be close at the
  OMNIbus server.
  
  
  
  If a situation is distributed to two agents attached to
  different RTEMS and the situation is true on both agents, two
  ITM events associated with the situation will be forwarded to
  the OMNIBus server/event listener, one for each managed system.
  If one of the agents is un-assigned from the situation, it will
  generate a 'P' (situation stopped) and 'D' (situation deleted)
  for the agent for that RTEMS. The current rule shipped with
  Situation Update Forwarded to handle the 'D' (situation deleted)
  events does not consider the TEMS thrunode, therefore the open
  event originated from the agent attached to the other RTEMS is
  also closed.
  
  
  
  Related Files and Output: None.
  

Local fix

Problem summary

• ITM situation events with 'D' status (situation deleted) can
  cause the same situation be closed on OMNIbus even if originated
   from a different thrunode.  The itm_event_clear trigger closes
  all open ITM Events with the same situation name, regardless of
  the thrunode.   For example, un-assigning a management system
  from a situation causes raised events from the same situation
  distributed to agents attached to other RTEMS to be closed at
  the OMNIbus server.
  
  The fix for this APAR is contained in the Event Synchronization
  update located in the service pack tec directory. See the
  6.3.0.7-TIV-ITM-SP-EventSync.README located in that directory
  for more information about installing this fix.
  

Problem conclusion

• The itm_event_clear trigger in the itm_db_update.sql file has
  been updated so that when processing 'D' status events it will
  close other situations only from the same thrunode.
  
  Install Actions:
  --------------------
  The Situation Update Forwarder is installed using the
  ESynch3000xxx.bin or upgraded using ESUpgrade30xxx.bin (where
  xxx is the operating system).   Once installed/updated, the
  updated itm_db_update.sql file will be installed into the
  Situation Update Forwarder omnibus directory.  From there, the
  file should be copied and loaded into the Object Server
  database.    See "Updating the OMNIbus database schema on
  signle-tier or aggregation tier ObjectServers"
  (https://www.ibm.com/support/knowledgecenter/en/SSTFXA_6.3.0.2/c
  om.ibm.itm.doc_6.3fp2/install/config_omni2_dbschema.htm) for
  more details.
  
  Below is an example of loading the file usign the nco_sql
  command:
      $OMNIHOME/bin/nco_sql -user username
    -password password
    -server server_name
    < path_to_file/itm_db_update.sql
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | service pack | 6.3.0.7-TIV-ITM-SP0003
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels