DB2 - Problembeschreibung
Problem IC90465 | Status: Geschlossen |
PERFORMANCE DEGRADATION MIGHT BE NOTICED WITH NOT EXISTS SUBQUERY WITH MULTIPLE TABLES. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
Under some scenarios, DB2 might choose a suboptimal plan if the following conditions are true: 1. The query has a not exists subquery 2. The subquery contains 2 or more base tables 3. The correlated join predicate in the subquery has an index on the join column. | |
Problem-Zusammenfassung: | |
Under some scenarios, DB2 might choose a suboptimal plan if the following conditions are true: 1. The query has a not exists subquery 2. The subquery contains 2 or more base tables 3. The correlated join predicate in the subquery has an index on the join column. | |
Local-Fix: | |
Disable AntiJoin by either : 1> db2set DB2_ANTIJOIN=NO -im 2> set up an optimization guideline to disable the antijoin for this specific query only. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 10.1 Fix Pack 3. | |
Workaround | |
Disable AntiJoin by either : 1> db2set DB2_ANTIJOIN=NO -im 2> set up an optimization guideline to disable the antijoin for this specific query only. | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC95335 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 25.02.2013 06.05.2014 06.05.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 | |
10.1.0.4 |