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 IT00386 Status: Geschlossen

SQL QUERY CONTAINS NOT EXISTS SUBQUERY AND NODENUMBER PREDICATE MIGHT
PRODUCE AN INCORRECT RESULT

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Under rare scenarios, DB2 might produce incorrect results if 
the following conditions are true: 
1) The query consists of one or more NOT EXISTS or NOT IN 
subqueries 
2) The parent side table of the subquery contains a nodenumber 
predicate 
 
eg.  select count(*) 
        from t1 
        where not exists (select 1 from t2 where t1.a=t2.a) and 
<-------------- condition 1 
                     nodenumber(t1.a)=1; 
<-------------- condition 2
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 101 fixpack 4                         * 
****************************************************************
Local-Fix:
1) Turn DB2_ANTIJOIN=NO 
2) Manually rewrite the query to form: 
select count(*) from t1 left join t2 on t1.a=t2.a where t2.a is 
null and nodenumber(t1.a)=1;
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem is fixed in DB2 version 101 fixpack 4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.03.2014
03.07.2014
07.04.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList