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

sqlrl_userTempPostCleanup gets sqlcode -901 ERROR AS A RESULT OF UNEXPECTED
CLEANUP ENTRIES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
DPF systems with applications that use both Declared Global 
Temporary Tables (DGTTs) and Created Global Temporary 
Tables (CGTTs) can encounter a problem where 
sqlrl_userTempPostCleanup() is called twice, once for DGTTs and 
once for CGTTs. A DGTT failure results 
in the skipping of the CGTT cleanup, which leads to unexpected 
cleanup entries on a subsequent cleanup.  The main symptom is a 
-901 error, the diaglog entry looks like the following: 
 
2012-02-14-09.47.09.961625-300 I26054932E884       LEVEL: Severe 
PID     : 11059                TID  : 47246934534464PROC : 
db2sysc 1 
INSTANCE: instname             NODE : 001          DB   : 
databasename 
APPHDL  : xxxxx                APPID: xx.xx.xx.xx.xx 
AUTHID  : authid 
EDUID   : 21999                EDUNAME: db2agent (databasename) 
1 
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: 49 
 sqlerrmc: sqlrl_userTempCleanup: unexpected cleanup entries 
 sqlerrp : SQLRL2C3 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFFFD      (6) 
0x00000001 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate:
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2FORLUW                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP2 or later                             * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
30.07.2013
30.07.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList