OA45678: FTO STAGE 3 DELETES ARE SOMETIMES REJECTED AT THE MIRROR

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• ********* START OF APAR OPEN TEMPLATE *********************
  * Please open an apar with the following severity and
  information:     *
  *
         *
  APAR Type:            Field
  Approver Initials:    RB
  Severity:             3
  Reported Release:     623
  Compid:               5724C04MS Tivoli Enterprise Management
  Server
  
  
  PROBLEM DESCRIPTION:
  The MIRROR HUB will fail to delete records during FTO stage III
  processing under certain circumstances. This issue is caused by
  a discrepancy that can occur relating to the timestamp in the
  record to be deleted. When this occurs, the MIRROR HUB will
  have records that have been deleted at the HUB.
  
  
  RECREATE INSTRUCTIONS:
  None.
  
  
  
  *************** END OF APAR OPEN TEMPLATE **********************
  

Local fix

• Recycle the MIRROR and HUB. This will prevent further
  occurrences. It will not correct the discrepancies at the
  MIRROR.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All TEMS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: FAULT TOLERANT OPTION CAN REJECT DELETE *
  *                      REQUESTS AT THE MIRROR MONITORING       *
  *                      SERVER                                  *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF.                               *
  ****************************************************************
  There are rare circumstances where a delete request fails to
  be performed at the MIRROR monitoring server.  This can
  result in contents of the various tables being out of sync
  between the hub monitoring server and the MIRROR monitoring
  server.
  Records that were not deleted at the MIRROR monitoring
  server can make their way back to the HUB monitoring server
  during fail over operations.
  

Problem conclusion

• The product has been modified to eliminate the rare
  circumstance where this issue can occur.
  

Temporary fix

Comments

APAR Information

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

  IV60288

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

Modules/Macros

• KQMM     KQMPRB
  

Fix information

• Fixed component name

  MGMT SERVER DS

• Fixed component ID

  5608A2800

Applicable component levels

• R630 PSY UA74413

     UP14/08/08 P F408

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.