home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC70489 Status: Geschlossen

REFRESH OF MQT ON VIEWS RETURN SQL0204N ON UPGRADED DATABASE IF BASE VIEWS
CALL COALESCE OR VALUE FUNCTION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
REFRESH TABLE of some MQTs may return SQL204N after upgrading to 
DB2 V9.7.  This will happen only if the MQT explicitly or 
implicitly references a view that contains a COALESCE or VALUE 
function.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users performing REFRESH TABLE of MQTs may after upgrading   * 
* to DB2 V9.7.                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* REFRESH OF MQT ON VIEWS RETURN SQL0204N ON UPGRADED DATABASE * 
* IF                                                           * 
* BASE VIEWS CALL COALESCE OR VALUE FUNCTION                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V97 FP3                                       * 
****************************************************************
Local-Fix:
1) For databases that have not been upgraded, upgrading these 
databases using a fix pack containing this fix will avoid this 
issue. 
2) Databases that have already been upgraded to v97.GA through 
v97 FP2 may encounter this issue.  Dropping and recreating the 
MQT will fix the issue.
verfügbare FixPacks:
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 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 9a 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
First fixed in Db2 V97 FP3
Workaround
1) For databases that have not been upgraded, upgrading these 
databases using a fix pack containing this fix will avoid this 
issue. 
2) Databases that have already been upgraded to v97.GA through 
v97 FP2 may encounter this issue.  Dropping and recreating the 
MQT will fix the issue.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.08.2010
24.09.2010
24.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList