IBM Support

IZ72222: FEDERATED QUERY HAVING SCALAR CORRELATED SUBQUERY PREDICATE COULD RETURN INCORRECT RESULT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Federated query having scalar correlated subquery predicate
    could return incorrect result.
    
    Here are some conditions which could cause this -
    
    1. It is a federated query.
    
    2. Query predicate involves scalar correlated subquery whose
       equivalent join columns contain unique key.
    
       A sample predicate is:
    
       "val_or_col_1 >= (select val_or_col_2 from subQTab where
       subQTab.c1 = outerTab.colX and subQTab.c2 = val_or_col_3)"
    
       The subquery equivalent join columns are (c1, c2). It
       requires primary key or unique index created on one or two
       out of (c1, c2).
    
    3. Regarding the parent SELECT operator of the scalar correlated
       subquery, the number of its join tables should be between 2
       and 9 inclusive, and each join table should have equivalent
       join predicate.
    

Local fix

  • If DB2COMPOPT registry is currently unset, issue "db2set
    DB2COMPOPT=0,16". Otherwise, consult DB2 service for further
    assistance.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Only federated queries along with the two additional         *
    * conditions which have to met (see "ERROR DESCRIPTION" for    *
    * details).                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Without this APAR, customer is exposed to the issue as       *
    * described in the "ERROR DESCRIPTION" section.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.1, Fixpack 9.                       *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 Version 9.1, Fixpack 9.
    

Temporary fix

  • If DB2COMPOPT registry is currently unset, issue "db2set
    DB2COMPOPT=0,16". Otherwise, consult DB2 service for further
    assistance.
    

Comments

APAR Information

  • APAR number

    IZ72222

  • Reported component name

    DB2 UDB ESE SOL

  • Reported component ID

    5765F4102

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-04

  • Closed date

    2010-04-16

  • Last modified date

    2011-01-21

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

    IZ72129

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

    IC66888

Fix information

  • Fixed component name

    DB2 UDB ESE SOL

  • Fixed component ID

    5765F4102

Applicable component levels

  • R910 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":"910"}]

Document Information

Modified date:
06 October 2021