DB2 FOR LUW / DB2FORLUW / 970 - DB2

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).

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 Fixpak 6                                  * 
****************************************************************

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in DB2 9.7 Fixpak 6

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC84480 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

01.03.2012
13.11.2012
13.11.2012

9.7.