Fixes are available
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod4 Fix Pack4 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 4 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows
APAR status
Closed as program error.
Error 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
Local fix
Address or correct all invalidated object and consider using SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS procedure.
Problem summary
**************************************************************** * USERS AFFECTED: * * All DB2 systems on all Linux, Unix and Windows platforms at * * service levels Version 11.1 GA through to Version 11.1 Fix * * Pack 1. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 11.1 Fix Pack 2 or see "Local Fix" * * portion for other suggestions. * ****************************************************************
Problem conclusion
The complete fix for this problem first appears in DB2 Version 11.1 Fix Pack 2 and all the subsequent Fix Packs.
Temporary fix
Comments
APAR Information
APAR number
IT20355
Reported component name
DB2 FOR LUW
Reported component ID
DB2FORLUW
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-04-25
Closed date
2017-06-23
Last modified date
2017-06-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
DB2 FOR LUW
Fixed component ID
DB2FORLUW
Applicable component levels
RB10 PSN
UP
RB10 PSY
UP
Document Information
Modified date:
04 May 2022