PK28044: FAILED RECOVERY DUE TO ZEROED UPDATE RECORD WHEN USING OPTIMIZE=Y ARCHIVED LOGS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The DB2 RECOVER utility may fail or data may be truncated when
  recovering a table using Optimized archived logs. This is due
  to needed Update records that have been zeroed during the
  Optimization process.
  

Local fix

• If dual logging is used and OPTIMIZE=Y is not being used on the
  second log, then the table can be recovered with this log.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Archive Log Accelerator.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: The  DB2  RECOVER utility may fail or   *
  *                      data may be truncated when recovering   *
  *                      a table using Optimized archived logs.  *
  *                      This is due to needed  Update records   *
  *                      that  have  been  zeroed  during  the   *
  *                      Optimization process.                   *
  ****************************************************************
  * 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

• ALC#OPT1
  

Fix information

• Fixed component name

  DB2 ARCHIVE LOG

• Fixed component ID

  5697I7300

Applicable component levels

• R220 PSY UK15969

     UP06/10/05 P F610

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.