DB2 - Problem description
Problem IC63972 | Status: Closed |
ENHANCE DIAGNOSTIC INFORMATION WHEN AGRESSIVELY FLUSHING PAGES FLUSHING LOGIC IS INVOKED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Reaching this point does not mean a code problem. Instead, this is a warning indicating that despite our earlier aggressive attempts to flush the bufferpool several times in a row we have failed to move up MinBuffLSN, which means that there must be an application holding up this hot dirty page for a longer period of time. There is nothing we can do about this; the application holding up the page should be investigated. We will produce some extended diagnostic information here. db2diag.log sample: 2009-05-05-19.58.56.871940-240 E90316E711 LEVEL: Warning PID : 12009 TID : 183045175872PROC : db2agent (SAMPLE) INSTANCE: db2inst1 NODE : 000 DB : RAWDB APPHDL : 0-11 APPID: *LOCAL.psustr.090505235827 AUTHID : PSUSTR FUNCTION: DB2 UDB, data protection services, sqlpgResSpace, probe:1270 MESSAGE : ZRC=0x00020173=131443=SQLB_FIXP "Page fixed during hard check point." DATA #1 : <preformatted> LSNs are: copyLowTran : 0000000003F3B5D6 copyMinBuff : 0000000003EDA3CE savedCurMinBuff: 0000000003EDA3CE flushlsn : 0000000003EE3FFB After flushing buffer pool: curMinBuff : 0000000003EDF3E6 copyNextLsn : 0000000003F63F36 | |
Problem Summary: | |
ENHANCE DIAGNOSTIC INFORMATION WHEN AGRESSIVELY FLUSHING PAGES FLUSHING LOGIC IS INVOKED. | |
Local Fix: | |
n/a | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First Fixed in DB2 LUW v9.7 Fixpack 1 and later. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.10.2009 15.12.2009 15.12.2009 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP1 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.1 |