When comparing Oracle dates to SQL Server I have found that it only works when the Oracle and SQL dates are strings.
Therefore in your Oracle query add a new column like this:
TO_CHAR(SYSDATE,'DD/MM/YYYY') as DATE_STRING
then in your SQL Server query add a new column:
CONVERT(VARCHAR(10), GETDATE(), 103) AS DATE_STRING
You can then map the columns in the Lookup Transform dialog.
Using the OLE DB Data Source for Oracle you will most likely come across this warning/error message when setting up your OLE DB Data Source:
The component reported the following warnings:
Warning at {EDFCB4B5-2102-4C54-8B8C-DC2362FDAB6B} [OLE DB Source [1]]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.
The fix is to exit the OLE DB Data Source and then examine its properties. Here you will find a AlwaysUseDefaultCodePage property. Set this to True and all will be good.
