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

QUERY MIGHT TRAP IN DATA PARTITION ELIMINATION OF A ZIGZAG JOIN

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
A query involving zigzag join might result in segmentation 
violation (SEGV) during data partition elimination phase 
(sqlri_datapart_elimination). The stack of the process will 
involve the following functions: 
 
       ossDumpStackTraceInternal 
       ossDumpStackTraceV98 
       OSSTrapFile::dumpEx 
       sqlo_trce 
       sqloEDUCodeTrapHandler 
       _intel_fast_memcmp 
       sqlrxcp2 
       sqlri_choose_tree_cmp 
       sqlri_datapart_elim_evalkey 
       sqlri_datapart_elim_set 
       sqlri_datapart_elimination 
       sqlriZZInit 
       sqlriZigZagJoin 
       sqlrihsjn 
       sqlriSectInvoke 
       sqlrr_smp_router 
       sqlrr_subagent_router 
       sqleSubRequestRouter 
       sqleProcessSubRequest 
       sqeAgent::RunEDU 
       sqzEDUObj::EDUDriver 
       sqlzRunEDU 
       sqloEDUEntry 
       pthread_tryjoin_np 
       clone 
 
To temporarily circumvent the issue, you can disable zigzag 
join: DB2_REDUCED_OPTIMIZATION=YES,ZZJN OFF either via db2set or 
via an optimizer profile so that it is applied only for 
this specific query.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to v111 mod 1 fixpack 1 or later                     * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
v111 mod 1 fixpack 1 and all future versions will contain the 
fix for this.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.09.2016
20.12.2016
20.12.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
11.1.1.1 FixList