DB2 - Problem description
Problem IT23929 | Status: Closed |
THE TO_DATE FUNCTION IS NOT PUSHED DOWN CORRECTLY IN FEDERATED SETUP | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
In the federated setup, function to_date is not pushed down below SHIP operator. Problem can be observed with following SQL: create nickname nname1 for fedserver.db2inst1.tab1 select * from nname1 where c3 BETWEEN to_date('2017-06-30', 'YYYY-MM-DD', 0)-2 MONTHS AND '2017-06-30' During execution of the above query, only part of the SQL is passed to federated data source. Following is observed in the access plan: RMTQTXT : (Remote statement) SELECT A0."C3" C0, A0."C1" C1, A0."C2" C2 FROM "DB2INST1"."TAB1" A0 WHERE (A0."C3" | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 10.5 Fix Pack 10 or higher * **************************************************************** | |
Local Fix: | |
To workaround the problem, following mapping has to be created: CREATE FUNCTION MAPPING {mapping_name} FOR "SYSIBM"." | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : follow-up : IT23930 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.02.2018 19.07.2018 19.07.2018 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |