IC33026: ANS0328E RC45 MERGE TEST FAILURE WITH CHANGE IN MANAGEMENT CLASS

APAR status

• Closed as Permanent restriction.

Error description

• TDP for MS SQL may fail with:
  ANS0328E (RC45)   The specified objects failed the merge test.
  if the customer attempts to change the management class that
  backups are bound to.  This will only occur if the meta data and
  bitfile data objects have different copy destinations.
  .
  Please ensure the customer is running at the latest TDP for MS
  SQL PTF 2.2.1.0 to address IC31372.  If a merge failure occurs
  because of a change in management classes, and the meta data and
  bitfile data are going to different copy destinations, data loss
  can occur.  Please see IC31372 for additional details.
  .
  Please also ensure the customer is at the 4.2.1.12 or higher
  API to address APAR IC31617, which can further compound the
  possibility of running into a situation where IC31372 could
  occur.  Please see IC31617 for additional details.
  .
  Initial Severity:  Low
  .
  Additional Keywords:
  mergeErrorFixup Microsoft
  

Local fix

• Do not change the management class that TDP for MS SQL backups
  are bound to if multiple copy destinations are used.  If a
  management class change is necessary, create a new nodename and
  perform a full backup with the new management class settings
  using that nodename for all future backups.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: TDP for MS SQL may fail with:           *
  *                      ANS0328E (RC45)   The specified         *
  *                      objects failed the merge test.          *
  *                      if the customer attempts to change      *
  *                      the management class that               *
  *                      backups are bound to.  This will only   *
  *                      occur if the meta data and              *
  *                      bitfile data objects have different     *
  *                      copy destinations or if the             *
  *                      VEREXIST, VERDELETE, RETONLY,           *
  *                      RETEXTRA values change.                 *
  *                      for the management class.               *
  ****************************************************************
  * RECOMMENDATION: Ensure that the policy settings and          *
  *                 management class settings are set up         *
  *                 correctly before running backups.            *
  ****************************************************************
  This is a limitation of the current design.
  This problem is caused by the fact that TDP for SQL needs
  to maintain logical integrity of multiple TSM objects
  within a single transaction. The problem is compounded
  by the fact that you can not have backup objects
  within a single transaction span different
  copy destinations. TDP for SQL uses temporary
  objects across multiple transactions for the initial
  backup. It then creates a single transaction to rename
  all of those objects to their proper TSM object name.
  The problem comes in when the management class has changed
  from the previous backup, and the new objects have
  different copy destintations.
  

Problem conclusion

• This limitation in the current design will need to be
  changed in order to address this unique situation.
  

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

Applicable component levels