IBM Support

IT03388: INCORRECT INDEX SCAN OUTPUT AFTER ROLLFORWARD OF LOAD ... INDEXI NG MODE REBUILD FOLLOWED BY LOAD ... INDEXING MODE INCREMENTAL.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The error does not happen on HADR environments.
    
    After ROLLFORWARD, data stored in table and in index is out of
    sync. Data scan vs index scan will return different results
    (data is the correct one). Index may have some records missing,
    but all records in index are present in table.
    
    The scenario is rollforward through (both LOADs must be in
    rollforward window, and operate on same table).
    LOAD COPY YES ... INDEXING MODE REBUILD
    LOAD COPY YES ... INDEXING MODE INCREMENTAL
    
    ROLLFORWARD of LOAD COPY YES ... INDEXING MODE INCREMENTAL must
    mark indexes bad, as the COPY image does not contain any index
    data.
    Under certain scenarios (see below), index may not be marked
    bad.
    
    Rollforward window must include LOAD COPY YES ... INDEXING MODE
    REBUILD and LOAD COPY YES ... INDEXING MODE INCREMENTAL.
    At least one LOAD ... REBUILD must precede LOAD ... INCREMENTAL.
    Problem does not happen when LOAD ... REBUILD is the last LOAD.
    

Local fix

  • Force index rebuild. Either drop/recreate index, or mark index
    bad explicitly.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users performing rollforward thru load copy image.       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 V10.1 Fixpack 5 or higher.                    *
    ****************************************************************
    

Problem conclusion

  • Firstly fixed in DB2 V10.1 Fixpack 5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT03388

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-25

  • Closed date

    2015-07-14

  • Last modified date

    2015-07-14

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

    IT03115

  • 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

  • RA10 PSY

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 10.1

Reference #: IT03388

Modified date: 14 July 2015