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

DB2 MIGHT PRODUCE INCORRECT RESULTS FOR QUERY WITH MULTIPLE QUANTIFIED
SUBQUERIES IN OR PREDICATE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Under rare scenarios, DB2 might produce incorrect results if the 
following conditions are true: 
1) The query contains 2 or more quantified subqueries. There are 
subqueries of the form ALL, ANY, SOME 
2) The subqueries are part of an OR predicate 
3) The result set within one or more subqueries is empty 
 
eg. 
select * from t1 where 
(exists (select * from t3 where t1.c1 = t3.c1) OR 
 c1 = ANY (select c1 from t4));
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 Cancun Release 10.5.0.4                * 
****************************************************************
Local Fix:
db2set -im DB2COMPOPT=NO_EORE
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Fixed in DB2 Cancun Release 10.5.0.4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.06.2014
03.11.2014
03.11.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList