PM64987: SLB ENTRIES IN THE CLONED BSDS ARE NOT ALWAYS BEING ERASED BY DB2UPDATE COMMAND.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• SLB entries in the cloned BSDS are not always being erased by
  the DB2UPDATE command.
  When there have been more than 50 BACKUP SYSTEM commands done on
  the source DB2 only part of the SLB entries in the cloned BSDS
  are being erased.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Cloning Tool.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: SLB entries in the cloned BSDS are not  *
  *                      always being erased by the DB2UPDATE    *
  *                      command. When there have been more      *
  *                      than 50 BACKUP SYSTEM commands done on  *
  *                      the source DB2 only part of the SLB     *
  *                      entries in the cloned BSDS are being    *
  *                      erased.                                 *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

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:

Modules/Macros

•    CKZ00224
  

Fix information

• Fixed component name

  DB2 CLONING TOO

• Fixed component ID

  5655N1000

Applicable component levels

• R310 PSY UK79145

     UP12/06/12 P F206

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.