|
Problem IT35236
|
Status: Closed |
DATE PRECISION IS LOST WHEN REMOTE SQL SHIPPED TO FEDERATED DB AND RESULTS IN 0 ROWS.
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
It is the same issue as v11.5 APAR IT34960.
federated DB:
Oracle
db2set:
DB2_COMPATIBILITY_VECTOR=ORA
problem:
When the below types of where predicate is sent by DB2 to
federated Oracle DB , there is no results returned by db2.
in the below example the 'remote statement' prepared & sent by
DB2 to Oracle is:
Example:
select * from tab1 t where TRUNC(CURRENT_DATE) - t.run_time >
2/(24*60)
In the explain we see that Remote statement:
RMTQTXT : (Remote statement):
Where (0.001388888888888888888888888888888889 < EXTRACT(DAY FROM
(TRUNC(TO_TIMESTAMP(:H1 )) - A0."RUN_TIME")))
the root cause for the wrong result (no date return) of bad
query is we tried to convert DATE INTERVAL type result of
TRUNC(CURRENT_DATE) - t.RUN_TIME to the number of days using "
EXTRACT(DAY FROM...)" in Oracle, but EXTRACT could only get the
DAY part of the date interval, not the number of days for the
whole interval in Oracle. For example DATA INTERVAL +000000000
19:58:59.000, EXTRACT(DAY FROM +000000000 19:58:59.000) will get
0, not 0.832627315.
This cause the wrong result and thus 0 rows returned. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* 11.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V11.1.4.6 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* 11.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V11.1.4.6 *
**************************************************************** |
| Comment |
DATE PRECISION IS LOST WHEN REMOTE SQL SHIPPED TO FEDERATED DB
AND RESULTS IN 0 ROWS. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.12.2020
15.06.2021
15.06.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
