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

QUERY WITH AN UNREFERENCED COMMON TABLE EXPRESSION WHICH REFEREN CES AN SQL
TRANFORM FUNCTIONS MAY TERMINATE ABNORMALLY UNDER CER

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 may terminate abnormally when a query with a Common Table 
Expression (CTE) satisfies all of the following conditions: 
 1. an SQL scalar function is referenced in the query, 
 2. the subquery in the CTE requires the compilation of an SQL 
transform function, 
 3. the CTE mentioned in step 2 is not referenced anywhere in 
the query. 
 
 -------Frame------ ------Function + Offset------ 
0x09000000263D7B50 
sqlns_expand_sql_fncs_in_opr__FP9sqlnq_oprP3loc + 0xEF0 
0x09000000263D9444 
sqlns_expand_sql_fncs_in_qur__FP9sqlnq_qurP3loc + 0x464 
0x0900000026396B58 sqlns_qgs__FP9sqlnq_qur17sqlnq_requestTypePc 
+ 0x818 
0x090000002633BC64 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_enviT7PP9sqlnq_qur 
+ 0x5C84 
0x090000002633E664 
sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq 
lrr_cmpl_env 
+ 0x64 
.... 
 
Local Fix: 
  1. remove the unreferenced CTE from the query, or 
  2. add a reference to the CTE in the query.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* NA                                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 3 or later.              * 
****************************************************************
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.02.2010
21.10.2010
21.10.2010
Problem solved at the following versions (IBM BugInfos)
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