|
Problem IC76448
|
Status: Closed |
INSERT OR UPDATE WITH INDEX COMPRESSION AND PAGE SPLIT HIGH/LOW MAY CAUSE CRASH DURINGINDEX PAGE SPLIT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If the indexes for a table are compressed and were created with
the PAGE SPLIT HIGH or PAGE SPLIT LOW clause, then any of the
following operations can cause a crash:
- INSERT
- UPDATE
- IMPORT (with the INSERT option)
- LOAD (with the INDEXING MODE INCREMENTAL or INDEXING MODE
AUTOSELECT options)
The following are example db2diag.log for the crash:
2011-05-17-12.22.23.341693-240 I23888A517 LEVEL: Severe
PID : 28180562 TID : 1838 PROC : db2sysc
INSTANCE: dbuser NODE : 000 DB : WSDB
APPHDL : 0-49 APPID: *LOCAL.dbuser.110517162100
AUTHID : DBUSER
EDUID : 1838 EDUNAME: db2agent (WSDB)
FUNCTION: DB2 UDB, index manager, sqlisplt, probe:600
MESSAGE : Split failed to make room!
DATA #1 : Hexdump, 4 bytes
0x070000000E3F5A78 : 0000 0004 ....
2011-05-17-12.22.23.342299-240 I24406A515 LEVEL: Severe
PID : 28180562 TID : 1838 PROC : db2sysc
INSTANCE: dbuser NODE : 000 DB : WSDB
APPHDL : 0-49 APPID: *LOCAL.dbuser.110517162100
AUTHID : DBUSER
EDUID : 1838 EDUNAME: db2agent (WSDB)
FUNCTION: DB2 UDB, index manager, sqlisplt, probe:1300
RETCODE : ZRC=0x87090054=-2029453228=SQLI_PRG_ERR "Program
error" DIA8575C An index manager programming error occurred. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* If the indexes for a table are compressed and were created *
* with the PAGE SPLIT HIGH or PAGE SPLIT LOW clause, then any *
* of the following operations can cause a crash: *
* - INSERT *
* - UPDATE *
* - IMPORT (with the INSERT option) *
* - LOAD (with the INDEXING MODE INCREMENTAL or INDEXING MODE *
* AUTOSELECT options) *
* *
* The following are example db2diag.log for the crash: *
* *
* 2011-05-17-12.22.23.341693-240 I23888A517 LEVEL: *
* Severe *
* PID : 28180562 TID : 1838 PROC : *
* db2sysc *
* INSTANCE: dbuser NODE : 000 DB : WSDB *
* APPHDL : 0-49 APPID: *
* *LOCAL.dbuser.110517162100 *
* AUTHID : DBUSER *
* EDUID : 1838 EDUNAME: db2agent (WSDB) *
* FUNCTION: DB2 UDB, index manager, sqlisplt, probe:600 *
* MESSAGE : Split failed to make room! *
* DATA #1 : Hexdump, 4 bytes *
* 0x070000000E3F5A78 : 0000 0004 .... *
* *
* 2011-05-17-12.22.23.342299-240 I24406A515 LEVEL: *
* Severe *
* PID : 28180562 TID : 1838 PROC : *
* db2sysc *
* INSTANCE: dbuser NODE : 000 DB : WSDB *
* APPHDL : 0-49 APPID: *
* *LOCAL.dbuser.110517162100 *
* AUTHID : DBUSER *
* EDUID : 1838 EDUNAME: db2agent (WSDB) *
* FUNCTION: DB2 UDB, index manager, sqlisplt, probe:1300 *
* RETCODE : ZRC=0x87090054=-2029453228=SQLI_PRG_ERR "Program *
* error" DIA8575C An index manager programming error occurred. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7.0.5. *
**************************************************************** |
| Local Fix: |
Drop and recreate the affected index without the PAGE SPLIT
HIGH/LOW clause.
Or alternatively use the ALTER INDEX command with the COMPRESS
NO, following by using the REORG INDEXES command to recreate the
problem index as uncompressed.
Or alternatively run "db2set DB2_INDEX_COMPRESSION=OFF" followed
by db2stop/db2start to pick up this change, then drop and
recreate the indexes. |
| available fix packs: |
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 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
|
| Solution |
The problem is first fixed in DB2 9.7.0.5. |
| Workaround |
Drop and recreate the affected index without the PAGE SPLIT
HIGH/LOW clause.
Or alternatively use the ALTER INDEX command with the COMPRESS
NO, following by using the REORG INDEXES command to recreate the
problem index as uncompressed.
Or alternatively run "db2set DB2_INDEX_COMPRESSION=OFF" followed
by db2stop/db2start to pick up this change, then drop and
recreate the indexes. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.05.2011
08.12.2011
08.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.0.5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
