Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC63914 Status: Geschlossen

UNNECESSARY U LOCK ON CATALOG ROW DURING REFRESH MQT TABLE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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;
verfügbare FixPacks:
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

Lösung
Problem First Fixed in DB2 Version 9.7 Fix Pack 1.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.10.2009
08.04.2010
02.02.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.1.FP1,
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.1 FixList