DB2 - Problem description
Problem IC96472 | Status: Closed |
IN A RARE SCENARIO, REPLICATED MQTS ARE NOT EXPLOITED TO IMPROVE PERFORMANCE OF QUERIES | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
In certain complex conditions using the Data Partition Feature (DPF), replicated MQTs are not exploited to improve performance of queries. The Extended Explain Information section of the db2exfmt output may show : Diagnostic Identifier: 2 Diagnostic Details: EXP0062W The following MQT or statistical view was not eligible because one or more columns or expressions referenced in the query were not found in the MQT: "<schema>"."<replicated mqt name>". The following is an example of the conditions required for this problem: 1. Queries contain EXISTS or IN subquery in the predicates, 2. The objects outside of the subquery in the queries are complex views, 3. The complex views reference tables in which there are replicated MQTs defined for those tables. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade the database server to v9.7 Fix Pack 10 or above * **************************************************************** | |
Local Fix: | |
Rewrite the subquery to a semantic equivalent using GROUP BY clause e.g. IN ( SELECT DISTINCT COL FROM BASETABLE ) can be rewritten to : IN ( SELECT COL FROM BASETABLE GROUP BY COL ) | |
Solution | |
This problem was first fixed in v9.7 Fix Pack 10 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC97348 IC97349 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.09.2013 08.12.2014 08.12.2014 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.10 |