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 IC64617 Status: Closed

V91FP9 - SPATIAL MIGRATION FAILS IF THERE ARE CUSTOMER STORED PROCEDURES
USING SPATIAL OBJECTS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The customer was attempting to migrate a database created and 
spatially-enabled on DB2 V8 to DB2 V9.1. 
 
The 'db2se migrate' utility failed due to a package dependency 
on spatial objects due to current design checks. 
 
We should allow package dependencies and perform rebind at the 
end of the spatial migration process
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Spatial Extender                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Attempting to perform spatial migration of a database which  * 
* has user-created stored procedures referencing Spatial       * 
* Extender objects will fail with a message like:              * 
* ***CAN NOT BE MIGRATED ***                                   * 
* : Package "DWA"."P6040277" --> Table                         * 
* "DB2GSE"."GSE_SPATIAL_REFERENCE_SYSTEMS"                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply V9.7 FP2                                               * 
*                                                              * 
* A work-around is to manually drop the stored procedures that * 
* reference Spatial Extender objects, perform the spatial      * 
* migration and re-create the stored procedures.               * 
****************************************************************
Local Fix:
available fix packs:
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 6 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 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
Fixed in V9.7 FP2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.11.2009
08.04.2010
08.04.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList