Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC63914 Status: Closed

UNNECESSARY U LOCK ON CATALOG ROW DURING REFRESH MQT TABLE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When a REFRESH TABLE MQT1 statement is executed, U-lock may be 
acquired unnecessarily on the catalog rows of other MQTs (call 
them MQTi) if all of the following conditions are satisfied: 
(1) MQTi shares at least one base table with MQT1 
(2) a. MQT1 is an immediate MQT and MQTi is a deferred MQT OR 
      b. both MQT1 and MQTi are deferred MQTs and the clause 
"USING REFRESH DEFERRED TABLES" is not specified in the REFRESH 
TABLE statement
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* -                                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP1 or higher                             * 
****************************************************************
Local Fix:
If both MQT1 and MQTi are deferred MQTs and the clause "USING 
REFRESH DEFERRED TABLES" is not specified in the REFRESH TABLE 
statement, U lock on MQTi can be avoided by temporarily turning 
off routing to deferred MQT before the REFRESH TABLE statement. 
For example: 
set current refresh age 0; 
REFRESH TABLE MQT1; 
set current refresh age any;
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows

Solution
Problem First Fixed in DB2 Version 9.7 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.10.2009
08.04.2010
02.02.2012
Problem solved at the following versions (IBM BugInfos)
9.1.FP1,
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList