|
Problem IT07152
|
Status: Closed |
SQL1034C, SQLSTATE=58031. DATABASE SHUTDOWN DUE TO INDEX ERROR DURING PAGE SPLIT ON COMPRESSED INDEX. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When using index compression, an error may occur when inserting
into the table that leads to a forced database shutdown. No
permanent damage will be introduced into the index object or any
other database object.
If the problem is hit, the db2diag.log will contain errors like
the following:
2015-02-13-11.04.22.075143-300 I63016E560 LEVEL: Severe
PID : 27322 TID : 46913005021504 PROC : db2sysc
INSTANCE: dbusr1 NODE : 000 DB : DB2DB
APPHDL : 0-22 APPID: *LOCAL.ztoth.150213160434
AUTHID : DBUSR1 HOSTNAME: myHost
EDUID : 18 EDUNAME: db2agent (DB2DB)
FUNCTION: DB2 UDB, index manager, sqlisplt, probe:600
MESSAGE : Split failed to make room!
DATA #1 : Hexdump, 4 bytes
0x00002AAAC8FFAE5C : 0400 0000
....
2015-02-13-11.04.22.075417-300 I63577E558 LEVEL: Severe
PID : 27322 TID : 46913005021504 PROC : db2sysc
INSTANCE: dbusr1 NODE : 000 DB : DB2DB
APPHDL : 0-22 APPID: *LOCAL.ztoth.150213160434
AUTHID : DBUSR1 HOSTNAME: myHost
EDUID : 18 EDUNAME: db2agent (DB2DB)
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: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1.0.5. *
**************************************************************** |
| Local Fix: |
To avoid the problem specify COMPRESS NO when creating indexes.
To deal with existing compressed indexes, do one of the
following:
- Use the DROP INDEX statement to drop the compressed index and
recreate it using the CREATE INDEX statement with the COMPRESS
NO option.
- Use the ALTER INDEX statement with the COMPRESS NO option for
every compressed index on the table and then issue the REORG
INDEXES command to rebuild existing compressed indexes as
uncompressed.
If the problem has been hit, execute the RESTART DATABASE
command (or simply reconnect to the database) to drive crash
recovery. Note that executing the exact same INSERT statement
immediately after crash recovery has completed might result in
the same problem being hit again. If that is the case, consider
dropping and recreating the index as uncompressed. |
| Solution |
The problem is first fixed in DB2 version 10.1.0.5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.02.2015
16.06.2015
16.06.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
