|
Problem IT20351
|
Status: Closed |
DB2 CHECK UPGRADE TOOL RETURNING WARNING ABOUT DISCONTINUED FUNCTION SYSFUN.ASCII1. |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
Customer will get the following warning from db2ckupgrade for
upgrading to v11.1:
DBT5534W Discontinued routine upon which the object depends:
"SYSFUN.ASCII1".
The warning was caused by SYSFUN.ASCII (CHAR) with specificname
ASCII1 being removed from V11.1 incorrectly. Consequently, when
upgrading database from any release to V11.1, any user object
that depends on this particular function will be invalidated. |
| 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. *
**************************************************************** |
| Local Fix: |
After database upgrade, the user should calls
SYSPROC.ADMIN_REVALIDATE_DB_OBJECT to revalidate the user object
so that the user object will pick up and depend on
SYSFUN.ASCII(VARCHAR) instead. |
| available fix packs: |
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
|
| Solution |
The complete fix for this problem first appears in DB2 Version
11.1 Fix Pack 2 and all the subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.04.2017
23.06.2017
23.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
