Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC95426 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 and Fix Pack 4 or higher.        * 
****************************************************************
Local-Fix:
1. Remove fetch first n rows clause 
2. Add order by clause to the subquery.
verfügbare FixPacks:
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

Lösung
Problem was first fixed in DB2 version 10.5 and Fix Pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.08.2013
08.09.2014
08.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList