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

DECLARE GLOBAL TEMP TABLE IN XA TRANSACTIONS MAY FAIL WITH SQL0901N OR
CAUSE TCB LEAK

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Running XA transactions having Declare Global Temporary Tables 
may show following symptoms : 
 
1) In DPF environment , concurrent XA transactions may result in 
sql0901 errors. The db2diag.log reports severe error that the 
table ID already exists and FODC_AppErr report is generated as 
well: 
 
2011-09-09-10.16.54.685400-420 I338342A680     LEVEL: Severe 
PID     : 758298               TID  : 26786    PROC : db2sysc 0 
INSTANCE: db2inst              NODE : 000      DB   : SAMPLE 
APPHDL  : 0-9953               APPID: 
REMOTE01.INA400.C858FC1BA635 
AUTHID  : DB2USER 
EDUID   : 26786                EDUNAME: db2agntp (DWP01) 0 
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 
29 
DATA #4 : String, 8 bytes 
Token = 
DATA #5 : unsigned integer, 2 bytes 
 
2) In serial or DPF enviroments increase in dbheap may occur, 
potentially leading to out of memory errors . In db2diag.log , 
following messages may be seen , 
 
2013-08-16-14.00.09.492599+540 I1613A582        LEVEL: Error 
PID     : 6750266              TID  : 69651     PROC : db2sysc 0 
INSTANCE: db2inst              NODE : 000       DB   : SAMPLE 
APPHDL  : 0-54720              APPID: 
10.91.64.163.51840.130814195803 
AUTHID  : DB2USER 
EDUID   : 69651                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_add_curr_activity, 
probe:200 
RETCODE : ZRC=0x8B0F0002=-1961951230=SQLO_NOMEM_DBH 
          "No memory available in 'Database Heap'" 
          DIA8302C No memory available in the database heap. 
 
3) When issuing db2stop , one may see dump.bin was created and 
may see following messages in db2diag.log. 
 
2013-01-24-03.32.26.633578+540 E54375A448       LEVEL: Warning 
PID     : 15466716             TID  : 12796     PROC : db2sysc 0 
INSTANCE: db2inst              NODE : 000       DB   : SAMPLE 
APPHDL  : 0-3 
EDUID   : 12796                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, data protection services, sqlpterm, 
probe:2290 
DATA #1 : <preformatted> 
Detected db2stop in progress.  Will wait up to 299 seconds to 
complete log archives. 
 
2013-01-24-03.32.26.635965+540 I54824A391       LEVEL: Severe 
PID     : 15466716             TID  : 12796     PROC : db2sysc 0 
INSTANCE: db2inst              NODE : 000       DB   : SAMPLE 
APPHDL  : 0-3 
EDUID   : 12796                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, data management, sqldTermDBCB, probe:5850 
MESSAGE : DMS Database Termination: Temp TCB still exists: 
 
2013-01-24-03.32.26.636085+540 I55216A440       LEVEL: Severe 
PID     : 15466716             TID  : 12796     PROC : db2sysc 0 
INSTANCE: db2inst              NODE : 000       DB   : SAMPLE 
APPHDL  : 0-3 
EDUID   : 12796                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_string (secondary 
logging fu, probe:0 
MESSAGE : SQLD_TCB: 
DATA #1 : String, 35 bytes 
Temp Table(4:829)=SESSION .TBHI1902 
 
2013-01-24-03.32.26.636226+540 I55657A213         LEVEL: Severe 
PID:15466716 TID:12796 NODE:000 Title: 
SQLD_TCB_NAME.tcbSchemaName 
Dump File: 
/database/insthome/db2inst/sqllib/db2dump/15466716.12796.000.dum 
p.bin
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 9.7 Fix Pack 6                    * 
****************************************************************
Local Fix:
As a workaround, follow the steps below: 
 
1. Stop db2 instance 
 
db2stop 
or 
 
hastopdb2 
 
2. Set the registry: 
 
db2set APM_THROTTLE=30 
 
3. Start db2 instance 
 
db2start 
or 
 
hastartdb2
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 was first fixed in Version 9.7 Fix Pack 6
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84571 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.01.2012
11.06.2012
29.10.2013
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 FixList