DB2 - Problem description
Problem IT16660 | Status: Closed |
IN SOME CIRCUMSTANCES REVALIDATION OF INVALIDATED VIEWS MAY NOT SUCCEED | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When a view: a) is dependent on another view which is replaced with an MQT or table thus invalidating it and b) makes use of a UDF During revalidation the SQL text of the view may be corrupted preventing the revalidation from completing. This occurs whether SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS or direct view access drives the revalidation. Direct revalidation will typically raise an SQL0104N error and SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS will report an SQL0361W warning, however in the SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS case the view text in SYSCAT.VIEWS is corrupted too (this does not occur with direct access revalidation). The corruption is of the last 8 bytes of the complete statement text as submitted so a comment at the end of the SQL may be all that is corrupted, if such a comment exists; revalidation will not report an error in this situation. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 Fix Pack 9 * **************************************************************** | |
Local Fix: | |
Drop and recreate the view manually. | |
Solution | |
First Fixed in DB2 10.5 Fix Pack 9 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.08.2016 08.05.2017 08.05.2017 |
Problem solved at the following versions (IBM BugInfos) | |
9.0. | |
Problem solved according to the fixlist(s) of the following version(s) |