home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC63647 Status: Closed

LOAD FAILS WITH SQL3005N INSTEAD OF SQL1218N,WHEN BUFFERPOOL IS FULL ON ONE
OF THE NODE IN A DPF ENVIRONMENT.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
User received SQL3005N Processing was interrupted, when the 
bufferpool on one of the node was full. The load should have 
failed with SQL1218N. This happens only on a DPF env. 
 
2009-04-19-14.49.42.719381-240 E370436E553         LEVEL: Error 
PID     : 13833                TID  : 186298394976 PROC : 
db2sysc 5 
INSTANCE: xx             NODE : 005          DB   : sample 
APPHDL  : 1-31721              APPID: 
10.4.43.110.6534.090419184925 
AUTHID  : xx 
EDUID   : 70143                EDUNAME: db2agntp (WISEQA) 5 
FUNCTION: DB2 UDB, Common Trace API, sqlbFreeUpSlot, probe:122 
MESSAGE : ADM6019E All pages in buffer pool "IBMDEFAULTBP" (ID 
"4098") 
are 
          in use.  Refer to the documentation for SQLCODE -1218. 
 
2009-04-19-14.49.42.723316-240 I370990E532         LEVEL: Severe 
PID     : 13833                TID  : 186298394976 PROC : 
db2sysc 5 
INSTANCE: xx            NODE : 005          DB   : sample 
APPHDL  : 1-31721              APPID: 
10.4.43.110.6534.090419184925 
AUTHID  : xx 
EDUID   : 70143                EDUNAME: db2agntp (WISEQA) 5 
FUNCTION: DB2 UDB, Common Trace API, sqlbFreeUpSlot, probe:0 
DATA #1 : String, 97 bytes 
Could not fix page for objID=20444, tbspaceID=8, objType=0, 
parentObjID=20444 parentTbspaceID=8.
Problem Summary:
LOAD FAILS WITH SQL3005N INSTEAD OF SQL1218N,WHEN BUFFERPOOL IS 
FULL ON ONE OF THE NODE IN A DPF ENVIRONMENT.
Local Fix:
available fix packs:
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 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
First fixed in DB2 V9.7 fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.10.2009
05.05.2011
05.05.2011
Problem solved at the following versions (IBM BugInfos)
9.1.FP3,
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList