suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT38399 Status: Closed

WRONG RESULT WHEN DB2 QUERY HAS CORRELATED EXISTS PREDICATE

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
Db2 query may generate wrong result when the following
conditions are met:

-There is an EXIST subquery predicate

-The subquery predicate has correlation

-There is unique index on the correlated column of the
predicate.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.5 FP7 or later                                 *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.5 FP7 or later                                 *
****************************************************************
Comment
Upgrade to 11.5 FP7 or later
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.09.2021
22.11.2021
09.12.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)