Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC63947 Status: Closed

WHEN STMM TURNED ON, ERRORS FROM DB2PFCHR PROCESS ARE REPORT IN
DB2DIAG.LOG

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
AIX 64 bit 5.3.0.0 
Server is running MPP/EEE "DB2 v9.1.0.2", "s070210", "U810940", 
and Fix Pack "2". 
When STMM is enabled in db cfg 
Self tuning memory                    (SELF_TUNING_MEM) = ON in 
the db cfg. 
After that following errors appear in the db2diag.log from a 
prefetcher. 
Here are the errors 
2007-04-29-08.31.55.843286-300 E497541A366        LEVEL: Error 
PID     : 1221176              TID  : 1           PROC : 
db2pfchr 0 
INSTANCE: db2p27               NODE : 000 
FUNCTION: DB2 UDB, Common Trace API, sqlbFreeUpSlot, probe:122 
MESSAGE : ADM6019E  All pages in buffer pool "BP4" (ID "6") are 
in use.  Refer 
          to the documentation for SQLCODE -1218.
Problem Summary:
WHEN STMM TURNED ON, ERRORS FROM  DB2PFCHR PROCESS ARE REPORT 
IN DB2DIAG.LOG
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
Fixed in V97 FP1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
05.02.2010
05.02.2010
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 FixList