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

GIVE HIGHER PRIORITY TO GROUP-BY MQT AND STATISTICAL VIEW IN OPTIMIZER PLAN
COSTING DECISION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When compiling a query, optimizer can generate multiple access 
plans that use different compilation of MQTs and use statistical 
view to adjust the cardinality of matched query join operators. 
Replicated MQT is commonly used in DPF and it can be enforced by 
either registry control 
"DB2_EXTENDED_OPTIMIZATION=FORCE_REPLICATED_MQT_MERGEA" or 
optimizer guideline "<MQTENFORCE TYPE='REPLICATED'/>" . A 
replicated MQT must have no aggregation. MQT having GROUP BY 
operation is called group-by MQT. When a base table has both 
replicated MQT and group-by MQT dependent on it, if replicated 
MQT is enforced and group-by MQT is not enforced, optimizer used 
to prune group-by MQT plan since it doesn't use the replicated 
MQT which is enforced. However the enforcement of replicated MQT 
should be in effect only at deciding among plans of base object 
access including base table and non-group-by MQTs and should not 
be applied to group-by MQT plan. This fix allows group-by MQT 
plan to be used if its plan costing is not more expensive than 
the base object access plan. 
 
This fix also increases of chance of using statistical view in 
optimizer planing. Query compiler attempts to substitute some 
subquery block with group-by MQT and adjust the cardinality of 
some other subquery block by using the matched statistical view. 
The group-by MQT used to reduce optimizer's use of statistical 
view. That is fixed by this APAR.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 7                               * 
****************************************************************
Local-Fix:
N/A
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 V9.7 Fix Pack 7
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC89174 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.05.2012
17.12.2012
17.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP7
Problem behoben lt. FixList in der Version
9.7.0.7 FixList