IT24744: CRASH RECOVERY MIGHT FAIL OR INTRODUCE DATABASE CORRUPTION WHEN USING AN ENCRYPTED DATABASE

Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod4 Fix Pack4 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 4 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• The issue only happens on encrypted databases.  In rare cases,
  asynchronous page-cleaner agents might incorrectly flush
  modified pages to disk before the corresponding log records have
  been flushed to disk.  This is in violation of Db2's write-ahead
  logging protocol.  If a database crash occurs while a page has a
  change on disk whose corresponding log record is not on disk,
  then the subsequent crash recovery might fail or it might
  complete successfully while leaving database objects in an
  inconsistent state.  This might result in a wide variety of
  errors or might cause Db2 to return incorrect results.
  

Local fix

• Run db2dart or INPSECT to examine the database after running
  crash recovery on an encrypted database.  To turn encrypted
  database to un-encrypted can be done by restore.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
  ****************************************************************
  

Problem conclusion

• First fixed in Db2 11.1 Mod 4 Fixpack 4
  

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

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RB10 PSN

     UP