DB2 FOR LUW / DB2FORLUW / 970 - DB2

In data partitioning feature (DPF) environments, there is a 
small timing window where an INSERT into a table will abnormally 
terminate with SQL1034C if running concurrently with CREATE 
INDEX DDL on the same table.  This can only happen if the index 
being created is a spatial index (defined on a spatial column of 
the table). 
 
Here is an example of the insert statement failing: 
 
insert into dwa.test values(1, db2gse.st_point(1,1,1)) 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL1034C  The database is damaged.  All applications processing 
the database 
have been stopped.  SQLSTATE=58031 
 
The following db2diag.log message will identify this issue: 
 
FUNCTION: DB2 UDB, Abstract Data Type, sqlyk_xformInit, probe:50 
MESSAGE : sqlyk_xformInit: keyXformCBEPtr is NULL. 
DATA #1 : Hexdump, 4 bytes 
0x00002AD33EBFAE70 : 0700 3087 
..0. 
 
The following stack can also help identify this problem: 
0x00002AD325DAEC47 sqloDumpEDU + 0x0037 
  (/home/hotel67/mladen/sqllib/lib64/libdb2e.so.1) 
0x00002AD3275B7E0D _Z10sqly_erroriiiPc + 0x0111 
  (/home/hotel67/mladen/sqllib/lib64/libdb2e.so.1) 
0x00002AD3275CD06C _Z21sqly_severe_pgm_erroriiPc + 0x0028 
  (/home/hotel67/mladen/sqllib/lib64/libdb2e.so.1) 
0x00002AD3275CAE06 
_Z15sqlyk_xformInitP8sqeAgentP8SQLD_KEYS2_P9SQLD_IXCBPP18sqlyk_k 
ey_xform_cbP16SQLB_OBJECT_DESC 
+ 0x010a 
  (/home/hotel67/mladen/sqllib/lib64/libdb2e.so.1) 
0x00002AD3275CBBA7 
_Z18sqlyk_addExtInxKeyP8sqeAgentP9SQLD_IXCBP12SQLI_KEYDATAPP14SQ 
LP_LOCK_INFOiP8SQLD_KEYPmmP18sqlyk_key_xform_cbP13SQLD_DFM_WORK 
+ 0x0153 
  (/home/hotel67/mladen/sqllib/lib64/libdb2e.so.1) 
0x00002AD3275CEC0E 
_Z17sqlyk_insertIndexP8sqeAgentP9SQLD_IXCBP12SQLI_KEYDATAP13SQLD 
_DFM_WORKPP14SQLP_LOCK_INFOPmmP8SQLD_KEY 
+ 0x012e 
  (/home/hotel67/mladen/sqllib/lib64/libdb2e.so.1) 
0x00002AD323EE9BC6 
_Z13sqldKeyInsertP13SQLD_DFM_WORKP16SQLD_TABLE_CACHES2_P13SQLD_T 
DATARECim 
+ 0x0e90 
  (/home/hotel67/mladen/sqllib/lib64/libdb2e.so.1) 
0x00002AD323EEEB00 
_Z13sqldRowInsertP8sqeAgenttthmiPP10SQLD_VALUEP13SQLD_TDATARECP8 
SQLZ_RID 
+ 0x17dc 
  (/home/hotel67/mladen/sqllib/lib64/libdb2e.so.1) 
0x00002AD32656AB48 
_Z8sqlrinsrP8sqlrr_cbttitPP10SQLD_VALUEmP8SQLZ_RID + 0x00b8 
  (/home/hotel67/mladen/sqllib/lib64/libdb2e.so.1) 
0x00002AD32661213D _Z8sqlriisrP8sqlrr_cb + 0x068f

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Version 9.7 GA through to Fix Pack 1 for Linux, Unix * 
* and Windows servers, using the data partitioning feature,    * 
* executing CREATE INDEX DDL concurrently with DML.            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The database manager system left a timing window open where  * 
* executing sections may be operating on objects which did not * 
* exist during compile time.  This problem is only encountered * 
* in DPF environments, where the index is defined on a spatial * 
* column of the table.                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Avoid running CREATE INDEX statements on spatial columns     * 
* concurrently with DML on the same table.  Otherwise, apply   * 
* DB2 Version 9.7 Fix Pack 2.                                  * 
****************************************************************

Create all spatial indexes before performing any 
inserts, updates, or deletes on the table.  Ensure not to run 
DML statements on the table concurrently while creating the 
indexes.

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
 

Problem is first fixed in DB2 Version 9.7 Fix Pack 2 and all 
subsequent Fix Packs.

keiner bekannt / siehe Local-Fix

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

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

13.04.2010
10.06.2010
10.06.2010

9.7.FP2