IBM Support

IC76448: INSERT OR UPDATE WITH INDEX COMPRESSION AND PAGE SPLIT HIGH/LOW MAY CAUSE CRASH DURINGINDEX PAGE SPLIT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error 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.
    

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.
    

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.                                      *
    ****************************************************************
    

Problem conclusion

  • The problem is first fixed in DB2 9.7.0.5.
    

Temporary 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.
    

Comments

APAR Information

  • APAR number

    IC76448

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-17

  • Closed date

    2011-12-08

  • Last modified date

    2011-12-08

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
08 December 2011