IBM Support

PI72800: INCORRECT FILTER FACTOR FOR PARTITION KEY OF VOLATILE TABLE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2 may calculate a incorrect filter factor for using BETWEEN
    and RANGE predicates, when a volatile table is defined as
    partitioned with one limit key.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of DB2 11 for z/OS who have                        *
    * queries that include more than one range                     *
    * predicate on the same column of a volatile                   *
    * table                                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * DB2 can underestimate the compound                           *
    *  filter factor of two range predicates                       *
    *  on the same column of a volatile table                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If a volatile table has more than one local range predicate on
    
    the same column, and one range filter factor is calculated by
    
    one method while the other range filter factor is calculated
    
    by a different method, DB2 could underestimate the compound
    
    filter factor of the two range predicates if the sum of the
    
    two range filter factors is less than 1.
    
    
    
    Example SQL:
    
    SELECT * FROM T1
    
    WHERE T1.C1 > 0
    
    AND T1.C1 < ?;
    
    
    
    If table T1 is a volatile table, and the sum of the filter
    
    factors for the two range predicates is less than 1, DB2 11
    
    will get 1/tablecard as the compound filter factor of the
    
    two range predicates.
    
    
    
    Additional Keywords:
    
    SQLPERFORMANCE SQLACCESSPATH FILTERFACTOR SQLRANGE
    

Problem conclusion

  • Code is updated to get a more reasonable compound filter factor
    for the problem above.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI72800

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-25

  • Closed date

    2016-12-28

  • Last modified date

    2017-02-01

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

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

    UI43588

Modules/Macros

  • DSNXOCCF
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI43588

       UP17/01/13 P F701

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":"12.0","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":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 February 2017