IBM Support

IV49070: EVENT SYNC OUT OF SYNC ERRORS WHEN ORIGINAL EVENT IS RESET

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • INTEGRATION DETAILS:
    ITM 6.2.3 FP 3 integrated with Omnibus 7.3
    
    
    SUMMARY OF PROBLEM:
    Customer is receiving several "Omnibus and OMEGAMON were out of
    sync for situation" errors a day, and currently has 1200 of
    these events in the
    Object Server.
    
    
    PD ALREADY PERFORMED:
    
    Modified the itm_deduplication trigger as follows -
    
    -- Handle Reset of situations
          elseif ( (new.ITMStatus = 'N') and (new.ITMIntType = 'U')
    )
          then
             if (debug_itmsync = 1)
             then
                write into itmfile (to_char( getdate() )+ ': Reset
    of Situation has been received.');
             end if;
             if (new.ITMEventData = 'DROP~')
             then
                   -- IZ70091 - Ignore this event, as it is from an
    agent switch
                   cancel;
    elseif ( (old.ITMStatus = 'Y') or (old.ITMStatus = 'A') )
    
    changed the last line above to -
    
    
    elseif ( (old.ITMStatus = 'Y') or (old.ITMStatus = 'A') or
    (old.ITMStatus = 'N') )
    
    This handles the case where the old ITMStatus='N' for closed and
    the new ITMStatus='N' for closed, then the event is updated
    instead of generating an error. Closed events were being
    received for events which were already closed, causing an
    unnecessary sync error. This change has reduced the number of
    sync errors the customer receives.
    

Local fix

  • Manually update itm_deduplication trigger
    

Problem summary

  • Synchronization error alerts are observed if a situation reset
    update is received for an event that had already been cleared.
    
    
    When a situation reset update alert is received in OMNIbus, and
    the original event has already been marked as reset, a
    synchronization error alert was generated.
    

Problem conclusion

  • DETAILS PENDING.
    If the situation is already marked as reset in OMNIbus, there is
     no need to generate a synchronization error event.
    
    The fix for this APAR is contained in the following maintenance
    packages:
    | fix pack | 6.3.0-TIV-ITM-FP0003
    

Temporary fix

  • Replace a line in the itm_deduplication trigger as described in
    the submit comments of the APAR.
    

Comments

APAR Information

  • APAR number

    IV49070

  • Reported component name

    TEMS

  • Reported component ID

    5724C04MS

  • Reported release

    623

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-09-17

  • Closed date

    2014-01-31

  • Last modified date

    2014-08-08

  • 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

  • R630 PSY

       UP



Document information

More support for: IBM Tivoli Monitoring V6
ITM Tivoli Enterprise Mgmt Server V6

Software version: 623

Reference #: IV49070

Modified date: 08 August 2014