|
Problem IC70489
|
Status: Closed |
REFRESH OF MQT ON VIEWS RETURN SQL0204N ON UPGRADED DATABASE IF BASE VIEWS CALL COALESCE OR VALUE FUNCTION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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. |
| available fix packs: |
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
|
| Solution |
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. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.08.2010
24.09.2010
24.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
