PI40776: BROKEN PAGES ERROR CODES X'0000' + '0C23' ON TARGET USING LOG APPLY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Broken Pages Error Codes X'0000'  + '0C23' on Target using LOG
  APPLY  may occur when using Fuzzy Copy option and high volume of
  activity on source objects.
  
  When DB2 objects are cloned with log apply during periods with
  large numbers of updates, errors may occur when the target
  objects are referenced. This is caused by the  broken  bit being
  set in one or more target pages. F broken  bit being set in one
  copied to the target DB2 subsystem using FUZZY-COPY, the target
  job is run to update pages with log records and fix the page
  OBIDs, etc. and the table space is REORGed. It s during the
  REORG process that DB2 may ABEND when one of more  broken  bits
  are found in the table space. This problem is caused by an
  incorrect start time used by log apply. This can result
  in log records being missed. The code has been changed to ensure
  the correct start time is used by log apply.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Cloning Tool.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Broken Pages Error Codes X'0000'        *
  *                      + '0C23' on Target using LOG APPLY      *
  *                      may occur when using Fuzzy Copy option  *
  *                      and high volume of activity on source   *
  *                      objects. When DB2 objects are cloned    *
  *                      with log apply during periods with      *
  *                      large numbers of updates, errors may    *
  *                      occur when the target objects are       *
  *                      referenced. This is caused by the       *
  *                      broken  bit being set in one or more    *
  *                      target pages. F broken  bit being set   *
  *                      in one copied to the target DB2         *
  *                      subsystem using FUZZY-COPY, the target  *
  *                      job is run to update pages with log     *
  *                      records and fix the page OBIDs, etc.    *
  *                      and the table space is REORGed. It      *
  *                      REORG process that DB2 may ABEND when   *
  *                      one of more  broken  bits are found in  *
  *                      the table space. This problem is        *
  *                      caused by an incorrect start time       *
  *                      used by log apply. This can result      *
  *                      in log records being missed. The code   *
  *                      has been changed to ensure the correct  *
  *                      start time is used by log apply.        *
  ****************************************************************
  * 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:

  UI32054

Modules/Macros

• CKZ#CARD CKZ#CNTL CKZ#LGAA CKZ#LGAC CKZ#LGAF CKZ#LGAI CKZ#LGAP
  CKZ#LRDR CKZ#LRD6 CKZ#MAIN CKZ#MLOG CKZ#RUNT CKZ#SUBD CKZ#WRIT
  CKZ00500 CKZ00501 CKZ00510 CKZ00527 CKZ00535 CKZ00545 CKZ00549
  CKZ00554 CKZ00612 CKZ00669 CKZ00710 CKZ00714 CKZ00717 CKZ00760
  CKZ00763 CKZ00764 CKZ00765 HCKZ310J
  

Fix information

• Fixed component name

  DB2 CLONING TOO

• Fixed component ID

  5655N1000

Applicable component levels

• R310 PSY UI32054

     UP15/10/20 P F510

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.