DB2 - Problem description
Problem IC88609 | Status: Closed |
AFTER RUNNING SPATIAL EXTENDER UPGRADE, CREATING A SPATIAL INDEX FAILS WITH -901. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
After running the Spatial Extender upgrade stored procedure, either directly or through the 'db2se upgrade' command, it is not possible to create a new spatial index. This fails with -901 and an error that some function can not be found although the name is not identified. Attempting to create a new feature layer with ESRI software will also fail. The spatial upgrade process attempts to drop and re-create most of the spatial objects with the most current definition. This is resulting in a corruption of the spatial index extension. This problem only occurs if there are spatial indexes already existing in the database, although this will usually be the case if a spatial upgrade is performed. The upgrade process will be successful if no spatial indexes exist at the time the upgrade is run. A work around is to save the current spatial index definitions and drop the spatial indexes, then run the upgrade followed by re-creating the spatial indexes. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 Spatial Extender * **************************************************************** * PROBLEM DESCRIPTION: * * After running the Spatial Extender upgrade stored procedure, * * it is not possible to create a new spatial index. This * * fails with -901 and an error that some function can not be * * found although the name is not identified. * **************************************************************** * RECOMMENDATION: * * Install V10.1 Fixpack 2 * **************************************************************** | |
Local Fix: | |
db2se save_indexes <dbname> db2se upgrade <dbname> db2se restore_indexes <dbname> | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Install V10.1 Fixpack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.11.2012 02.01.2013 02.01.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.2 | |
10.5.0.2 |