IBM Support

PI37614: MULTI-INDEX INTERSECTION ACCESS PATH SELECTED WITH REDUNDANT INDEX ACCESS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2 may incorrectly include an index to a multi-index
    intersection plan that provides the same matching coverage as
    another index and a subset of the screening coverage.  In this
    case, the index provides no additional value and should not be
    included in the multi-index intersection plan.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS users.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: DB2 may choose to include an index in   *
    *                      a multi-index intersection plan that    *
    *                      provides no value.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    DB2 may select a multi-index intersection access path that
    includes an index that doesn't provide any additional filtering
    benefit.  For example...
    
    SELECT ...
    FROM T1
    WHERE C1 LIKE ?
      AND C2 = ?
      AND C3 = ?
    
    With indexes IX1(C1,C2) and IX2(C1,C2,C3), there is no value
    in including both indexes in the multi-index intersection plan
    as IX2 alone will provide all of the filtering from IX1.
    
    Additional Keywords:
    SQLPERFORMANCE SQLACCESSPATH SQLMULTIINDEX
    

Problem conclusion

  • DB2 code has been changed to avoid adding a redundant index
    to a multi-index intersection plan.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI37614

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-03-23

  • Closed date

    2015-05-19

  • Last modified date

    2015-07-01

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

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

    UI27771 UI27772

Modules/Macros

  • DSNXOGCM
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI27771

       UP15/06/04 P F506

  • RB10 PSY UI27772

       UP15/06/04 P F506

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 July 2015