DB2 - Problem description
| Problem IT09013 | Status: Closed |
DB2 MIGHT PRODUCE INCORRECT RESULTS WHEN RUNNING QUERIES WITH EQUALITY TIMESTAMP PREDICATES | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
DB2 might produce incorrect results when running queries with
equality timestamp predicates
Description:
Under rare scenarios, DB2 might produce incorrect results if the
following conditions are true:
1) The query contains two or more subselects and tables
2) Each of these have atleast one column of type TIMESTAMP with
default precision 6
3) One or more of these columns are projected out from the
select
4) The columns also contains an equality predicate with a string
representation of timestamp
eg. Select *
from T1, (Select TS
from T2
where T2.TS = '2015-01-01 00:00:00') as
tmp
where T1.TS = '2015-01-01 00:00:00' and tmp.TS =
'2015-01-01 00:00:00' | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * First fixed in v9.7 fp11 * **************************************************************** | |
| Local Fix: | |
Workaround: 1) Turn on statement concentrator 2) Modify the query to introduce T1.TS = T2.TS predicate | |
| Solution | |
First fixed in v9.7 fp11 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.05.2015 21.10.2015 21.10.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP11 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.11 |
|