|
Problem IC63540
|
Status: Closed |
V91FP9 - SPATIAL MIGRATION FAILS IF THERE ARE CUSTOMER STORED PROCEDURES USING SPATIAL OBJECTS |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - 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.1 FP9. *
* *
* 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.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
Fixed in V9.1 FP9. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC64344 IC64617
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.10.2009
17.11.2009
17.11.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.9
|
 |
