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

DB2 might abend when executing queries with complex subselects and
existential subqueries

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Under rare circumstances, DB2 might trap with SEGV (signal 11) 
when the following conditions are true: 
 
1) The query contains one or more complex subselects, 
outerjoins, Group By, etc 
2) The query contains one or more correlated existential 
subqueries 
 
Stack Trace: 
6        sqlnr_constpu_action 
7        sqlnr_comp 
8        sqlnr_rcc 
9        sqlnr_perqun_action 
10       sqlnr_comp 
11       sqlnr_priority 
12       sqlnr_rcc 
13       sqlnr_allqun_action 
14       sqlnr_comp 
15       sqlnr_rcc 
16       sqlnr_start_action 
17       sqlnr_comp 
18       sqlnr_rcc 
19       sqlnr_exe
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 10.5 Fix Pack 7                           * 
****************************************************************
Local Fix:
Solution
First fixed in version 10.5 Fix Pack 7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.06.2015
05.02.2016
05.02.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