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 IC81624 Status: Closed

DGTT CREATION IN DPF ENVIRONMENT CAN RETURN -901 APPLICATION ERROR IF THERE
WAS A LOCK TIME OUT WHEN CLEANING UP A PRIOR DGTT

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
If there is a lock time out in sqlrl_userTempCleanup, a 
subsequent request to declare a global temporary table (DCTT) 
may fail with a -901 error. 
 
The problem is that on some nodes, the table id for the temp 
table my be available while not yet available on the other nodes 
yet.  When the next application tries to reserve a table id, one 
or more nodes may see this id as already being in use. 
 
This applies to DPF env only. 
 
 
The messages that could show up in the db2diag.log include: 
 
2011-10-02-04.37.48.498923-240 I5307128A520       LEVEL: Error 
PID     : 27066496             TID  : 68223       PROC : db2sysc 
17 
INSTANCE: db2inst1             NODE : 017         DB   : SAMPLE 
APPHDL  : 0-9021               APPID: *LOCAL.db2inst1.111002083 
AUTHID  : DB2INST1 
EDUID   : 68223                EDUNAME: db2agnta (SAMPLE) 17 
FUNCTION: DB2 UDB, catalog services, sqlrl_userTempCleanup, 
probe:10 
RETCODE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT 
          "LockTimeOut - tran rollback Reason code 68" 
 
 
2011-10-02-04.37.48.968954-240 I5307649A687       LEVEL: Severe 
PID     : 27066496             TID  : 29991       PROC : db2sysc 
17 
INSTANCE: db2inst1             NODE : 017         DB   : SAMPLE 
APPHDL  : 0-5058               APPID: *LOCAL.db2inst1.1110020838 
AUTHID  : DB2INST1 
EDUID   : 29991                EDUNAME: db2agntp (SAMPLE) 17 
FUNCTION: DB2 UDB, buffer pool services, sqlbReserveFileToken, 
probe:10 
DATA #1 : String, 80 bytes 
Error: ReserveFileToken was called to reserve a token that was 
already allocated 
DATA #2 : String, 9 bytes 
PoolID = 
DATA #3 : Pool ID, PD_TYPE_SQLB_POOL_ID, 2 bytes 
5 
DATA #4 : String, 8 bytes 
Token = 
DATA #5 : unsigned integer, 2 bytes 
38 
 
2011-10-02-04.37.49.019154-240 I5313895A879       LEVEL: Severe 
PID     : 27066496             TID  : 29991       PROC : db2sysc 
17 
INSTANCE: db2inst1             NODE : 017         DB   : SAMPLE 
APPHDL  : 0-5058               APPID: *LOCAL.db2inst1.1110020838 
AUTHID  : DB2INST1 
EDUID   : 29991                EDUNAME: db2agntp (SAMPLE) 17 
FUNCTION: DB2 UDB, catalog services, sqlrl_dgtt_rcv, probe:30 
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic 
error detected" 
          DIA8501C A buffer pool logic error has occurred. 
CALLED  : DB2 UDB, data management, sqldTableCreateTemp 
RETCODE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic 
error detected" 
          DIA8501C A buffer pool logic error has occurred. 
DATA #1 : String, 7 bytes 
ftoken 
DATA #2 : unsigned integer, 2 bytes 
38 
DATA #3 : String, 7 bytes 
ttoken 
DATA #4 : unsigned integer, 2 bytes 
5 
 
2011-10-02-04.37.49.022518-240 I5317424A864       LEVEL: Severe 
PID     : 27066496             TID  : 29991       PROC : db2sysc 
17 
INSTANCE: db2inst1             NODE : 017         DB   : SAMPLE 
APPHDL  : 0-5058               APPID: *LOCAL.db2inst1.1110020838 
AUTHID  : DB2INST1 
EDUID   : 29991                EDUNAME: db2agntp (SAMPLE) 17 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 33 
 sqlerrmc: sqlrl_dgtt_rcv: buffer pool error 
 sqlerrp : SQLRL1E9 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFFD8      (6) 
0x00000011 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate:
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.1 on Linux, Unix and Windows          * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 LUW Version 9.1 Fix Pack 12 or higher levels.  * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 LUW Version 9.1 Fix Pack 12.
Workaround
N/A
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.02.2012
27.04.2013
27.04.2013
Problem solved at the following versions (IBM BugInfos)
9.1.FP12
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.12 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.