DB2 - Problem description
Problem IC64344 | Status: Closed |
V91FP9 - SPATIAL MIGRATION FAILS IF THERE ARE CUSTOMER STORED PROCEDURES USING SPATIAL OBJECTS | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - 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.5 FP6 * * * * 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.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Solution | |
Fixed in V9.5 FP6 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.11.2009 22.04.2010 22.04.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) |