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

DB2 can trap in function sqlno_crule_nljn under rare circumstances

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
DB2 can trap during compiling a query under rare circumstances, 
when either one of the following conditions is true: 
 
- the query meets the criteria to be recognized as a star schema 
for the purposes of a zigzag join, and if the query includes 
more than one fact table with common associated dimension tables 
- the query contains XML path expressions 
 
The top of the stack contains the following functions: 
 
sqlno_crule_nljn 
sqlno_crule_join_choices 
sqlno_crule_join_order 
sqlno_crule_join_root 
sqlno_crule_join 
sqlno_gen_partitions_for_QTB 
sqlno_plan_end_opr
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 5                       * 
****************************************************************
Local Fix:
If the trapping query is eligible for zigzag join, then the 
problem can be worked around by disabling zigzag join, that is, 
by setting DB2_REDUCED_OPTIMIZATION=ZZJN OFF
Solution
First Fixed in DB2 Version 10.5 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.09.2014
13.03.2015
13.03.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList