|
Problem IC67440
|
Status: Closed |
DB2CKUPGRADE INCORRECTLY REPORTS SQL ROUTINES CREATED IN Version 8 AS EXTERNAL ROUTINES. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If the database has SQL routines created in Version 8, the
db2ckupgrade utility would report the following warning
ADM4100W The db2ckupgrade or UPGRADE DATABASE command identified
external routines or user-defined wrappers that could have
potential incompatibility with the multi-threaded database
manager. See the file alter_unfenced_<database_name>.lst that
contains the list of routines and wrappers identified, or a set
of statements to restore the routines or wrappers definition
altered by the UPGRADE DATABASE command.
The file alter_unfenced_<database_name>.lst would contain a list
of such SQL routines created in v8, although they are not
external routines. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who tries to run db2ckupgrade prior to upgrading their *
* databases from v8 to v9.7. *
****************************************************************
* PROBLEM DESCRIPTION: *
* If the database has SQL routines created in Version 8, the *
* db2ckupgrade utility would report the following warning *
* *
* ADM4100W The db2ckupgrade or UPGRADE DATABASE command *
* identified external routines or user-defined wrappers that *
* could have potential incompatibility with the multi-threaded *
* database manager. See the file *
* alter_unfenced_<database_name>.lst that contains the list of *
* routines and wrappers identified, or a set of statements to *
* restore the routines or wrappers definition altered by the *
* UPGRADE DATABASE command. *
* *
* The file alter_unfenced_<database_name>.lst would contain a *
* list of such SQL routines created in v8, although they are *
* not external routines. *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 v9.7 Fix Pack 4 or later. *
**************************************************************** |
| Local Fix: |
Users may ignore the warning as long as all the routines listed
in alter_unfenced_<database_name>.lst are verified to be not
external routines. |
| available fix packs: |
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
This problem is first fixed in DB2 v9.7 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC73614
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.03.2010
08.06.2011
09.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
