home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IT07861 Status: Geschlossen

CORRELATED EXISTENTIAL SUBQUERIES MIGHT BE DEPICT SLOW PERFORMANCE

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Under rare scenarios, DB2 might depict unoptimized query plan 
for queries when the following is true: 
1) The query contains one or more correlated subqueries 
2a) The subqueries are of the type NOT EXISTS/NOT IN 
2b) Alternatively, the subqueries are of the type EXISTS() or 
EXISTS() 
3) There are three or more tables in the outer subselect of the 
query. Atleast one of these tables is not correlated to the 
above subqueries 
4) The order of the joins between the outer tables places the 
correlated parent table as the last join.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.5 Fixpack 6 or Later.                 * 
****************************************************************
Local-Fix:
1) Rewrite the query to add redundant join predicates 
2) Use registry variable: db2set DB2COMPOPT=ALLOW_COMPLEX_SQ
Lösung
First Fixed in DB2 LUW v10.5 Fixpack 6.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.03.2015
26.08.2015
26.08.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.6 FixList