IBM Support

IZ90691: DB2 MAY RETURN INCORRECT RESULT FROM SELECT DISTINCT LEFT OUTER JOIN UNION ALL VIEW

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • An SQL statement to perform a left outer join between tables or
    views along with a UNION ALL view may return incorrect results.
    The UNION ALL view must be the right table or null-producing
    table of the left outer join. In addition, the SELECT clause
    must be specified with DISTINCT for the tables or views.
    
    
    The above mentioned scenario will likely cause DB2 to return
    more rows from the left outer joining process, than the optimum
    value.
    

Local fix

  • Run the following commands to stop DB2 instance, set the
    registry variable and restart DB2:
    
    db2stop force
    db2set DB2_UNION_OPTIMIZATION=DISABLE_OJPPD_FOR_NP
    db2start
    
    This will avoid optimization that can lead to incorrect results.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of Db2 V9.1, V9.5, V9.7                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * An SQL statement to perform a left outer join between tables *
    * or                                                           *
    * views along with a UNION ALL view may return incorrect       *
    * results.                                                     *
    * The UNION ALL view must be the right table or null-producing *
    *                                                              *
    * table of the left outer join. In addition, the SELECT clause *
    *                                                              *
    * must be specified with DISTINCT for the tables or views.     *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    *                                                              *
    * The above mentioned scenario will likely cause DB2 to return *
    *                                                              *
    * more rows from the left outer joining process, than the      *
    * optimum                                                      *
    * value.                                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to most current fix pack.                            *
    ****************************************************************
    

Problem conclusion

  • Fixed in fix pack 8.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ90691

  • Reported component name

    DB2 UDB ESE SOL

  • Reported component ID

    5765F4102

  • Reported release

    950

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-13

  • Closed date

    2011-06-30

  • Last modified date

    2011-06-30

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

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

    IC73692 IC73756

Fix information

Applicable component levels

  • R910 PSN

       UP

  • R910 PSY

       UP

  • R950 PSN

       UP

  • R950 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950"}]

Document Information

Modified date:
06 October 2021