DB2 FOR LUW / DB2FORLUW / B10 - DB2

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.

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

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.

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
 

First fixed in Db2 11.1 Mod 4 Fixpack 4

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

16.04.2018
27.11.2018
27.11.2018