IBM Support

IC99956: CONCURRENT REORGS ON DIFFERENT DATA PARTITIONS OF THE SAME PARTI TIONED TABLE MIGHT EXECUTE SEQUENTIALLY DURING IDXRECREAT PHASE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Once you execute concurrent REORG operations like:
    db2 "reorg table T1 allow no access on data partition PART0"
    db2 "reorg table T1 allow no access on data partition PART1"
    
    on table T1 meting criteria required for parallel reorg, you may
    notice that IdxRecreat phase is being sequential.
    The problem is caused by latching during the processing what
    prevents parallel execution.
    
    The problem can only be hit when INTRA_PARALLEL is turned on or
    when using database partitioning feature.
    
    Observable symptoms:
    1. You might notice unexpected difference between REORG finish
    times for partitions similar in size by observing REORG command
    finish time or db2pd -reorg output.
    2. You might notice in db2top output that only one REORG at the
    time utilizes IO, while REORG for other partitions are idle.
    3. In stacks collected during the issue occurrence, you can
    notice that one REORG thread is holding
    SQLO_LT_SQLD_TCB__loadInProgress latch, while other parallel
    threads are waiting for the latch in subject.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * INTRA_PARALLEL ON or when using DPF                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 version 9.7 fixpack 10                        *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 version 9.7 fixpack 10
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC99956

  • 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

    2014-03-10

  • Closed date

    2014-11-10

  • Last modified date

    2014-11-10

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

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

    IT00986 IT00987

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
10 November 2014