DB2 FOR LUW / DB2FORLUW / 970 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Spatial Extender users using 'db2se upgrade' command     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If a database created on DB2 V9.7 is upgraded to a current   * 
* fixpack level and the Spatial Extender 'db2se upgrade'       * 
* command is run, it is not possible to create new spatial     * 
* indexes, failing with a -901 error.                          * 
*                                                              * 
* For example:                                                 * 
* create index test on test(geom) extend using                 * 
* db2gse.spatial_index(1,0,0)                                  * 
* results in the messages                                      * 
* DB21034E  The command was processed as an SQL statement      * 
* because it was not a valid Command Line Processor command.   * 
* During SQL processing it returned:                           * 
* SQL0901N  The SQL statement failed because of a non-severe   * 
* system error.                                                * 
* Subsequent SQL statements can be processed.  (Reason         * 
* "function not found".)  SQLSTATE=58004                       * 
*                                                              * 
* If the spatial index is created by third-party application   * 
* software such as Esri ArcGIS, the failure will be reported   * 
* as an application error.                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP7                                      * 
****************************************************************

db2se save_indexes <dbname> 
db2se upgrade <dbname> 
db2se restore_indexes <dbname>

DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Upgrade to DB2 V9.7 FP7

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC83695 IC88609 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

25.03.2012
23.10.2012
23.10.2012

9.7.FP7