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

SUBQUERIES REFERENCING AN ALWAYS FALSE PREDICATE MIGHT NOTICE BAD
PERFORMANCE

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Under rare scenarios, a query executing on DB2 might take a long 
time if the following conditions are true: 
1) The query contains one or more subqueries of the type NOT 
EXISTS/NOT IN. 
2) The subqueries contains predicates which can be proven to be 
ALWAYS FALSE and 
produce an empty result set. 
 
eg. Select * from T1 
       Where Not Exists (select * from T2 
                                      where T1.c1 = T2.c1 and 
1=0)
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please update to DB2 Cancun Release 10.5.0.4                 * 
****************************************************************
Local-Fix:
Workaround: 
1) Manually rewrite the query to remove the subquery 
2) db2set -im DB2_ANTIJOIN=NO
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
The problem is fixed in DB2 Cancun Release 10.5.0.4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.01.2014
06.10.2014
06.10.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList