PM85238: INCORROUT MAY BE RETURNED WITH LIST PREFETCH ACCESS WHEN SOME NON-BOOLEAN TERM PREDICATES UNDER OR IS NOT THE MATCHING ONE

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Incorrect output may be returned when range list access path is
    chosen for the table and some non-boolean term predicates under
    OR is not the matching predicate, so the whole OR predicates
    need to be re-evaluated.
    
    Here is an example:
    index I1 on T1(C1, C2)
    
    (C1 = ? AND C2 > ?) OR  (C1 > ? AND C2=?)
    
    in the second branch, C2=? is not the matching predicates, we
    need to re-evaluate the whole predicate tree, this is the case
    that we might have incorrect output.
    
    Additional Keywords:  SQLINCORR SQLINCORROUT DB2INCORR/K
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 for z/OS version 10 users of SQL     *
    *                 statements with range list access and one    *
    *                 of the non-boolean term predicates under     *
    *                 OR is not the matching predicate.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect output may be returned when   *
    *                      a range list access path is chosen for  *
    *                      the table and one of non-boolean term   *
    *                      predicates under OR is not the matching *
    *                      predicate.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An example for incorrect output is shown below:
    
    index I1 on T1(C1,C2)
    (C1 = ? AND C2 > ?) OR (C1 > ? AND C2 = ?)
    
    In the second branch,c2 = ? is not the matching predicate,
    but was incorrectly chosen.Since the path was not re-evaluated
    as it should have been,incorrect output may occur.
    

Problem conclusion

  • DB2 has been modified to correctly process the aforementioned
    SQL statement,so there will be no incorrect output.
    
    Additional Keywords:  SQLINCORR SQLINCORROUT DB2INCORR/K
                          SQLRANGELIST SQLOR
    

Temporary fix

  • * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM85238

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-20

  • Closed date

    2013-04-24

  • Last modified date

    2013-06-04

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

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

    UK93759

Modules/Macros

  •    DSNXORGL
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK93759

       UP13/05/10 P F305

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.



Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM85238

Modified date:

2013-06-04

Translate my page

Machine Translation

Content navigation