home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC62056 Status: Closed

AFTER MIGRATING FROM V8.1 TO V9.7, SQL PROCEDURES THAT REQUIRE MANUAL
MIGRATION CANNOT BE IDENTIFIED BY QUERY IN INFOCENTER.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If you created your SQL procedures in DB2 UDB Version 8.1 and 
migrated from a DB2 UDB Version 8 32-bit instance to a DB2 
Version 9.7 64-bit instance, you must drop and re-create those 
SQL procedures as part of the manual migration process. 
 
However, during the migration to V9.7, SQL procedures created in 
V8.1 are changed to FENCED and cannot be identified by the 
following query in InfoCenter. 
 
Migrating SQL procedures 
 
  Procedure 
  2. Run the following query to identify the SQL procedures that 
you need to re-create: 
     SELECT procschema, specificname 
     FROM syscat.procedures 
     WHERE language = 'SQL' AND fenced = 'N' AND 
           substr(IMPLEMENTATION, 10,6) = 'pgsjmp'
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.7                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 1.                            * 
****************************************************************
Local Fix:
Use the following query instead to identify the SQL procedures 
that you need to re-create. 
 
SELECT procschema, specificname 
FROM syscat.procedures 
WHERE language = 'SQL' AND substr(IMPLEMENTATION, 10,6) = 
'pgsjmp'
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 9.7 FixPack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.07.2009
07.03.2010
07.03.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList