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 IT23907 Status: Closed

IN CDE, INCORRECT RESULTS MIGHT BE RETURNED FOR A QUERY THAT REFERENCES A
CORRELATED SCALARY SUBQUERY IN A PREDICATE

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Incorrect result might be returned when an access plan contains 
an RCTQ operator over a FILTER operator that is over a scalar 
subquery subplan. 
 
The following criteria must be satisfied to encounter the issue: 
- the query references a column organized table 
- there is a predicate comparing the result of a scalar subquery 
and a column from the column organized table 
- the scalar subquery is correlated
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CDE                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 Version 11.1 Modpack 3 Fixpack 3 or later     * 
****************************************************************
Local Fix:
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
Problem fixed in Db2 Version 11.1 Modpack 3 Fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
31.01.2018
15.03.2018
16.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)