|
Problem IC66862
|
Status: Closed |
FEDERATED QUERY HAVING SCALAR CORRELATED SUBQUERY PREDICATE COULD RETURN INCORRECT RESULT. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem 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. |
| 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.7, fixpack 2. *
**************************************************************** |
| Local Fix: |
If DB2COMPOPT registry is currently unset, issue "db2set
DB2COMPOPT=0,16". Otherwise, consult DB2 service for further
assistance. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 9.7, Fixpack 2. |
| Workaround |
If DB2COMPOPT registry is currently unset, issue "db2set
DB2COMPOPT=0,16". Otherwise, consult DB2 service for further
assistance. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.03.2010
30.06.2010
21.01.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
