IBM Support

IT10811: INDEX/DATA MISMATCH MIGHT OCCUR IN AN MDC TABLE AFTER A DEFERRED ROLLOUT IS SUSPENDED

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The error might occur when the following criteria are met:
    
    1) The table is an MDC table with at least two RID indexes.
    2) A deferred cleanup rollout delete is performed on that MDC
    table.
    3) Before the asynchronous index cleanup operation completes, it
    suspends due to lock timeout or deadlock, and another deferred
    cleanup rollout delete is performed on the table.
    4) As a result, it updates the block map incorrectly marking all
    rolled-out blocks as free even though the index cleanup is not
    complete. This might result in a variety of different index
    errors.  The problem can be detected by running the INSPECT
    command with the INDEXDATA option.
    
    You can see following output in db2diag.log when the async index
    cleanup suspends(3):
    
    EDUID   : 543210               EDUNAME: db2taskp (SAMPLE) 0
    FUNCTION: DB2 UDB, AIC, aicRolloutIndexCleanup, probe:2075
    MESSAGE : ADM9514I  BEGIN async index cleanup on table
    "DB2INST1.T1"
              (ID "123") and table space "TS1" (ID "5").
      ...
    
    
    EDUID   : 543210               EDUNAME: db2taskp (SAMPLE) 0
    FUNCTION: DB2 UDB, AIC, aicRolloutIndexCleanup, probe:4318
    MESSAGE : ZRC=0x82A90066=-2102853530=ABP_SUSPEND_TASK_PRO
              "Suspend the task processor"
    CALLED  : DB2 UDB, AIC, aicRolloutIndexCleanup
    

Local fix

  • If the problem occurs, rebuild the indexes.  To avoid the
    problem do not use deferred index cleanup.
    db2set DB2_MDC_ROLLOUT=IMMEDIATE
    

Problem summary

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

Problem conclusion

  • The problem is first fixed in DB2 version 9.7.0.11.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT10811

  • 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

    2015-08-20

  • Closed date

    2015-10-06

  • Last modified date

    2015-10-06

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

    IT10760

  • 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

       FIX



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IT10811

Modified date: 06 October 2015