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

QUERY CONTAINING EXISTS SUBQUERY AND FETCH FIRST N ROWS CLAUSE MIGHT
PRODUCE INCORRECT RESULTS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Under certain scenario, DB2 might produce incorrect results if 
the following conditions are true: 
1. The query contains an exists subquery 
2. The subquery has a fetch first n rows clause in the outer 
most subselect 
3. There is either a LOB column or a total column column width > 
32K in the query output list. 
 
Eg.: 
select P.lob 
from P 
where exists (select 1 from SQ where SQ.c1 = P.c1 fetch first 1 
rows only);
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2version 10.5 Fix Pack 3.                       * 
****************************************************************
Local Fix:
1. Remove fetch first n rows clause 
2. Add order by clause to the subquery.
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
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
First fixed in DB2 version 10.5 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
27.02.2014
27.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList