IBM Support

IC82353: INDEX CORRUPTION RESULTING FROM OPERATIONS ON DETACHED PARTITIONS FROM TABLE WITH PARTITIONED INDEXES

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • There are two problems here:
    
    1) This problem results in an empty index being created on the
    detach partition, despite the partition not being empty.  To hit
    this problem you need to detach a partition that has partitioned
    index(es) that require rebuilding.  If the asynchronous
    partition detach task does not fully complete and a crash occurs
    and then restart database is then executed and the database is
    configured to have indexes rebuilt on restart (controlled by the
    indexrec Database and Database Manager configuration
    parameters), it will then rebuild the problem indexes on each
    partition, but on the partially detached partition (still in the
    logically detached state), the index will be created empty.
    Later, once the database has been restarted the asynchronous
    partitioned detach task will complete the detach and the
    standalone table may have data with an empty index.
    
    2) This problem can result in an index on a non-partitioned
    table to be marked as unique in the catalogs but not in the
    actual index object (or the reverse, non-unique in the catalogs
    but unique in the actual index).  As a result it does not
    enforce uniqueness correctly.  The following is an example of
    how this can occur:
    - partitioned table with a non-unique partitioned index on not
    nullable columns where the index key columns are a super-set of
    the table partitioning key columns
    - a partition is detached and before the asynchronous portion of
    the partition detach completes
    - the table is altered to add a primary or unique key using the
    same columns, in the same order, as the partitioned index
    mentioned above (i.e. we will convert the existing index from
    non-unique to unique).  If at this point you dropped a primary
    or unique constraint, you may see experience the reverse of this
    issue (non-unique in the catalogs but unique in the actual
    index) provide that the index existed prior to the primary key
    or unique constraint being added to the table.
    - the asynchronous partitioned detach task completes and the
    detached partition is now a fully accessible standalone
    non-partitioned table where the catalogs and index object are
    inconsistent
    

Local fix

  • Recreate the affected indexes.
    

Problem summary

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

Problem conclusion

  • The problem was first fixed in DB2 version 9.7.0.6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC82353

  • 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

    2012-03-29

  • Closed date

    2012-06-05

  • Last modified date

    2012-06-05

  • 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



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC82353

Modified date: 05 June 2012