|
Problem IC77979
|
Status: Closed |
UPON DATABASE TERMINATION DURING ROLLFORWARD OR RECOVER PENDING,PAGE CLEANER MAY EXIT WITH A NON-EMPTY DIRTY LIST |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* see APAR description *
****************************************************************
* PROBLEM DESCRIPTION: *
* see APAR description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB 9.7 FixPack 6 *
**************************************************************** |
| Local Fix: |
None (none needed) |
| available fix packs: |
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
|
| Solution |
Problem first fixed in DB2 UDB 9.7 FixPack 6 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.08.2011
04.06.2012
04.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
