IBM Support

PK81115: INCORROUT (MORE ROW FOUND) ON QUERY WITH PARTITIONED INDEX AND IN-SUBQUERY WITH MAX FUNCTION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Incorrect output (more row found) when running a query, which
    refers to a table with partitioned Index and also contains
    IN-subquery with MAX().
    .
    Additional Symptoms: DB2INCORR/K
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 for z/OS V8 and V9 users who are     *
    *                 exploiting a DPSI index.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: When an access type is one fetch        *
    *                      access, and the index is a Data         *
    *                      Partitioned Secondary Index (DPSI),     *
    *                      incorrect output might occur due to the *
    *                      selection of the wrong access path.     *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Incorrect output might occur when a query is exploiting
    a DPSI index and ONE-FETCH index access is chosen.  This can
    been seen by examining the PLAN_TABLE after an Explain of the
    query.  Column ACCESSTYPE would contain 'I1' for a one-fetch
    index access.
    

Problem conclusion

  • Code was changed to ensure that the correct ordering is used
    for one-fetch access under the following scenario:
    - The query is using a DPSI index, and the access type is
       ONE-FETCH index access.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PK81115

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-02-20

  • Closed date

    2009-04-13

  • Last modified date

    2011-05-06

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

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

    UK45715 UK45716

Modules/Macros

  • DSNXOGP
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK45715

       UP09/05/12 P F905

  • R910 PSY UK45716

       UP09/05/12 P F905

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

Document Information

Modified date:
06 May 2011