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

DB2 MIGHT ABEND WHEN EXECUTING QUERY WITH INLIST PREDICATES

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Under rare scenarios, DB2 might abend if the following 
conditions are true: 
1) The query contains 4 or more INLIST predicates 
2) Atleast 2 predicates are based on the same column 
3) Atleast two INLISTs contain only constants 
4) Atleast two other INLIST contain complex expressions 
 
Trap file will show SIGSEGV in following stack: 
 
sqlnr_qsort_compare_inlist_exps 
qsort 
sqlnr_sinlist2common 
sqlnr_qrwprep_phase2 
sqlnr_prep2_action 
sqlnr_comp 
sqlnr_seq 
sqlnr_rcc 
sqlnr_exe 
sqlnn_cmpl 
sqlnn_cmpl 
sqlra_compile_var 
sqlra_find_var 
sqlra_get_var 
sqlrr_prepare
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 Fix Pack 7 or higher.            * 
****************************************************************
Local Fix:
Merge the INLISTs based on the same column into a single list
Solution
Fixed in DB2 version 10.5 Fix Pack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.02.2015
19.01.2016
19.04.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList