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

-901 REASON "EXPECTED TEMP TCB" ERROR MAY BE RAISED WITH REOPT
ALWAYS AND XML TEMP TABLES.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
An application that invokes an SQL statement operating with 
REOPT ALWAYS enabled, may suffer error SQL0901 with Reason 
string : 
"EXPECTED TEMP TCB" when the SQL statement involves the 
manipulation of XML temporary data. 
 
e.g. 
 
a stored procedure created with  "CALL 
SYSPROC.SET_ROUTINE_OPTS('REOPT ALWAYS')"  run prior to the 
procedure creation and 
code similar to this : 
 
CREATE PROCEDURE proc1 ( IN @inputxml XML ) 
... 
P1 : BEGIN 
 
   select * from XMLTABLE ( 'p ....  PASSING @inputxml as "p" 
....  ) 
 
( syntax not complete and just pasted for illustration ) 
 
... 
 
END P1 
 
Can fail with the error, if the input values ( @inputxml ) come 
from a non-permanent table.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the DB2 server side to V10.1 Fix Pack 2              * 
****************************************************************
Local Fix:
workaround : do not use REOPT ALWAYS.
available fix packs:
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
This problem has first been fixed in V10.1 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
06.05.2013
06.05.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList