|
Problem IT20413
|
Status: Closed |
DBT5555N THE DB2CKUPGRADE UTILITY FAILED BECAUSE THE DATABASE HAS ONE OR MORE INVALID OBJECTS. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
APAR IT17049 was opened to add checking of invalidated view and
MQT object into check upgrade tool (code went into 10.1 fp6,
10.5 fp9 and 11.1 m1fp1) to address a customer issue where
SQLCODE -440 was report during a 9.7 -> 10.5 database upgrade.
SQL0440N No authorized routine named
"DBMS_UTILITY.GETINDEXDEPENDENCY" of type "PROCEDURE" having
compatible arguments was found. LINE NUMBER=1. SQLSTATE=42884
The customer was advised to query syscat.invalidobject and found
invalidated MQT and views in 9.7. After they dropped the
invalidated MQT and views in 9.7 and the database upgrade is
successful. The customer was not able to provide us with the DDL
for the dropped MQT and views to repro. The customer requested
that we put a check into check upgrade tool to proactive warn
the user.
This checking is too wide and return error on any invalidated
view/MQT that will not even impact database upgrade.
Check upgrade tool will be tighten to only check for this
special condition as error:
an invalid view that has dependency on
DBMS_UTILITY.GETINDEXDEPENDENCY |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 9 or higher *
**************************************************************** |
| Local Fix: |
Address or correct all invalidated object and consider using
SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS procedure. |
| 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 :
| 28.04.2017
29.09.2017
29.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
