IBM Support

IT11870: RECOVERING A FAILED ONLINE INCREMENTAL LOAD ON AN INDEX CREATED WITH THE "PCTFREE 0" OPTION MIGHT CORRUPT THE INDEX

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This applies to any databases with the above specific condition.
    
    The problem can happen only if the index in question is defined
    with the "PCTFREE 0"
    option.  Then an online incremental load must be performed.
    During a very specific internal error scenario  and recovery,
    there is a chance that the index page could get corrupted
    and we end up with duplicate keys  on the page.
    
    Symptoms may include index-data mismatch or incorrect results.
    
    Running db2dart or inspect may be able to detect the problem.
    Look for duplicate key or key data mismatch error messages.
    

Local fix

  • To avoid hitting this problem as opposed to undo the corruption,
    the user can use db2dart /mi option to mark the index bad before
    recovering the failed load command.
    
    Applying the APAR fix will prevent the problem from occurring.
    
    If this problem is hit and the index is corrupted, then the
    solution is to use db2dart /mi to mark the index invalid and
    then the next access to the table will rebuild the index.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 10.1 Fix Pack 6                               *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 10.1 Fix Pack 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT11870

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-10-21

  • Closed date

    2017-03-02

  • Last modified date

    2017-03-02

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

    IT03122

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

    IT11884

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1"}]

Document Information

Modified date:
26 September 2021