IZ74289: FTO RECORDS NOT SYNCHRONIZED DURING STAGE III

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)
IBM Tivoli Monitoring 6.2.2 Fix Pack 6 (6.2.2-TIV-ITM-FP0006)

APAR status

• Closed as program error.

Error description

• Approver Initials:    RB
  
  PROBLEM DESCRIPTION:
  
  
  accesslist records can be dropped or ignored under the right
  timing
  circumstance between the HUB and MIRROR. Potentially other
  records types
  can be involved.
  
  
  RECREATE INSTRUCTIONS:
  

Local fix

• No workaround available
  

Problem summary

• In an FTO environment, some eiblog records are not synchronized
  on the MIRROR management server.  This is due to a mismatch in
  timestamp values when a batch of eiblog records are processed.
  

Problem conclusion

• Code in the FTO component has been changed to always insert new
  records to MIRROR management server tables.
  
  The fix for this APAR is included in the following maintenance
  vehicle:
      | fix pack | 6.2.1-TIV-ITM-FP0003
  

Temporary fix

• Recycle the HUB management server and MIRROR management server
  so that the MIRROR management server tables are synchronized.
  

Comments

APAR Information

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

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

  OA33584

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R621 PSY

     UP