DB2 - Problem description
Problem IC82503 | 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 / 950 - 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: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 UDB version 9.5 fixpack 10. * **************************************************************** | |
Local Fix: | |
No | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.04.2012 27.08.2012 27.08.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.10 |