DB2 - Problem description
Problem IC81751 | Status: Closed |
REFRESH MQT IN DPF ENVIRONMENT DOESN'T HONOR AN OPTIMIZATION LEVEL, PREVIOUSLY SET WITH SET CURRENT OPTIMIZATION LEVEL CMD | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Refresh MQT in DPF environment doesn't honor an optimization level, previously set with SET CURRENT OPTIMIZATION LEVEL statement. Usually setting lower optimization level is needed to avoid MQT routing during MQT refresh operation for a base table with number of MQT to reduce locking and increase concurrency. Lowering optimization level before REFRESH MQT statement in a single node environment works as expect, however in DPF environment current optimization level is not honored by other nodes thus having them to compile REFRESH MQT statement at the default optimization level (5). | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 9.7 Fixpak 6 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 9.7 Fixpak 6 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84480 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.03.2012 13.11.2012 13.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |