home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84543 Status: Closed

WHEN OPTIMIZER PLAN USES GROUP-BY MQT FOR AN INSERT STATEMENT, OPTIMIZER
(I.E. NON-GROUP-BY MQT) MAY NOT BE CONSIDERED.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
21.11.2012
21.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList