DB2 FOR LUW / DB2FORLUW / A50 - 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:                                              *
* Encrypted Databases only                                     *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Please, see error description and install this 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.

not known / see Local fix

forerunner  : 
follow-up : IT24968 

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

16.04.2018
16.07.2018
16.07.2018