DB2 - Problem description
Problem IC70649 | Status: Closed |
GUIDELINE MAY NOT BE APPLIED WHEN MQT USAGE IS ENFORCED USING A PROFILE OR DB2_EXTENDED_OPTIMIZATION=FORCE_REPLICATED_MQT_MERGE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
An optimizer plan guideline provided in an optimizer profile may not be applied if MQT usage enforcement is enabled. MQT usage enforcement can be enabled in one of 2 ways: - Using the FORCE_REPLICATED_MQT_MERGE option of the DB2_EXTENDED_OPTIMIZATION registry variable (for replicated tables) - In an optimizer profile using the <MQTENFORCE> element Specifically, for this issue to arise, following conditions must be satisfied: - MQT usage enforcement must be enabled - One or more tables referenced by the query must have dependent MQTs defined on them - The dependent MQTs can be matched semantically to the referenced based tables - Said tables must be referenced in the access plan guideline in an active optimizer profile by any of the elements listed under the "accessRequest" group in the CURRENT OPTIMIZATION PROFILE SCHEMA. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 4 or later. * **************************************************************** | |
Local Fix: | |
None exists, aside from either turning off MQT usage enforcement or by not issuing a guideline. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7 Fix Pack 4. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 19.08.2010 28.04.2011 28.04.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |