IBM Support

IT00425: POTENTIAL INDEX CORRUPTION WHEN USING INDEX COMPRESSION AND UNIC ODE DATABASES WHICH USE UCA COLLATION WITH S(STRENGTH) = 1 OR 2

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The follow criteria must be met for the potential of index
    corruption:
    - Must be an index using index compression and defined with a
    varying length data type in the index key (excluding binary
    strings and character strings of the FOR BIT DATA subtype)
    - Must be a Unicode databases which use UCA collation with
    S(strength) = 1 or 2
    - Must acquire an exclusive lock on the table within the same
    unit of
    work as deleting some data from the index (for example, the lock
    could be the result of escalation or the LOCK TABLE command),
    followed by rollback of the unit of work.
    
    The corruption will result in a key mismatch between the table
    and index and can manifest in different ways. However, it will
    most commonly show up during a subsequent delete operation with
    a message like the following:
    
    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 or command failed because of a
    database system
    error. (Reason "Key data mismatch encountered during key
    delete".)
    SQLSTATE=58004
    
    Note that this is a common symptom to other problems so seeing
    this is not conclusive that you hit this problem.
    
    Also note the corruption might go undetected for some time after
    being introduced.  To detect the problem you can run INSPECT
    with the INDEXDATA option.
    

Local fix

  • Rebuild the corrupt index using the REORG INDEX(ES) command.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 version 9.7.0.10.                             *
    ****************************************************************
    

Problem conclusion

  • The problem is first fixed in DB2 version 9.7.0.10.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT00425

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-20

  • Closed date

    2014-11-07

  • Last modified date

    2015-04-07

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

    IT00421

  • 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



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IT00425

Modified date: 07 April 2015