|
Problem IC84480
|
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 / A10 - DB2 |
| Problem description: |
Refresh MQT in DPF environement 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 V10.1 Fixpak 1 *
**************************************************************** |
| Local Fix: |
|
| 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 |
First fixed in DB2 V10.1 Fixpak 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
29.04.2013
29.04.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
