DB2 - Problembeschreibung
| Problem IC84543 | Status: Geschlossen |
WHEN OPTIMIZER PLAN USES GROUP-BY MQT FOR AN INSERT STATEMENT, OPTIMIZER (I.E. NON-GROUP-BY MQT) MAY NOT BE CONSIDERED. | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problembeschreibung: | |
The symptom is when optimizer plan uses Group-By MQT for an INSERT statement, optimizer (i.e. non-Group-By MQT) may not be considered. The optimizer MQT includes replicated MQT. This happens even if DB2_EXTENDED_OPTIMIZATION=FORCE_REPLICATED_MQT_MERGE is set in v9.7 | |
| Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users prior to DB2 V10 FP1 * **************************************************************** * PROBLEM DESCRIPTION: * * WHEN OPTIMIZER PLAN USES GROUP-BY MQT FOR AN INSERT * * STATEMENT, * * OPTIMIZER (I.E. NON-GROUP-BY MQT) MAY NOT BE CONSIDERED. * * * * * * The symptom is when optimizer plan uses Group-By MQT for an * * INSERT statement, optimizer (i.e. non-Group-By MQT) may not * * be * * considered. The optimizer MQT includes replicated MQT. This * * happens even if * * DB2_EXTENDED_OPTIMIZATION=FORCE_REPLICATED_MQT_MERGE is set * * in * * v9.7 * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 V10 FP1 * **************************************************************** | |
| Local-Fix: | |
No | |
| verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
| Lösung | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 14.06.2012 21.11.2012 21.11.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 10.1.0.1 |
|
| 10.5.0.1 |
|