DB2 FOR LUW / DB2FORLUW / 970 - DB2

A database that is either in the recover pending or rollforward 
pending state is being terminated. Part of this termination is 
flushing changed (a.k.a. dirty) buffer pool pages to the disk. 
Under extremely rare timing circumstances, a page cleaner may 
end up dispatching a batch of asynchronous IO requests for the 
dirty pages to be written out, but the page cleaner gets 
terminated before collecting these asynchronous IO requests back 
from the operating system. This will cause that the dirty 
list(s) where the dirty pages reside will never be cleaned up, 
and a message similar to the following one will be seen in the 
DB2 diagnostic log: 
 
2011-06-23-11.49.06.227093-420 I179122E1061        LEVEL: Severe 
PID     : 14755                TID  : 47851803502912PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 644                  EDUNAME: db2pclnr (SAMPLE) 
FUNCTION: DB2 UDB, buffer pool services, sqlbClnrTerm, probe:10 
DATA #1 : String, 68 bytes 
ClnrTerm: Exiting with a non-empty dirty list.Please contact 
askBPS. 
 
These messages should only have a cosmetic impact. Since the IO 
requests have been submitted to the operating system, they are 
not lost, the page cleaner merely fails to collect the requests. 
It should be noted that this is a very rare timing problem that 
has only been found during deep ad-hoc testing. The problem does 
not affect AIX unless the default AIO collect method (IOCP) is 
disabled via the DB2_USE_IOCP registry variable.

**************************************************************** 
* USERS AFFECTED:                                              * 
* see APAR description                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see APAR description                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB 9.7 FixPack 6                             * 
****************************************************************

None (none needed)

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem first fixed in DB2 UDB 9.7 FixPack 6

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

08.08.2011
04.06.2012
04.06.2012

9.7.FP6