November 12, 2013 at 8:44 pm
SQL Server is acting weird here. Source (Lotus Domino) have dirty data which looks as 0200-10-29 and alike. 10 char length, but year is wrong sometimes, still having 4 numbers. The Oracle can successfully import them, and when I import from Oracle to SQL Server also have no problem. Interesting part is, if I try to import from Lotus Domino directly to SQL Server it fails with error saying can't convert to date. Both Oracle and SQL server uses LEI (Lotus Enterprise Integrator) to push data to rdbms. Can anyone explain this why is it happening and any workaround? Using SQL Server 2008 R2 Enterprise here
November 12, 2013 at 11:31 pm
What are the date types in both databases?
Date you provided might be dirty in business logic, but not for all date types. It is just year 200.
November 12, 2013 at 11:52 pm
Data type in SQL Server is date in both cases. Previous data flow was Domino->Oracle->SQL Server, now getting direct Domino->SQL Server
November 13, 2013 at 6:26 am
I would guess that Oracle is performing an implicit conversion or the date is being interpreted incorrectly somewhere.
Have you checked the dates on the source system directly and compared the results in Oracle?
Worth remembering that the dates are stored as integers in SQL and not as presented through a GUI.
November 13, 2013 at 8:35 am
Did check the data, in Domino and Oracle looks same : '0200-10-29' and their type is date as well. As far as I know they are not converting it while Activity (etl) runs, looked at them. And as I said, if I import same table from Oracle, data flows smooth and get into SQL Server, but if I want to take to SQL Server from Domino it fails giving error..
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply