Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 SSIS and Import/Export (2008)
 SSIS 2008 R2(dataconversation OVERFLOWN)

Author  Topic 

kond.mohan
Posting Yak Master

213 Posts

Posted - 2012-05-18 : 09:14:14


I WANT to move the data from oracle to sql server using dataflowtask

one of my table column(dateformat existed like this way

1998-11-27 00:00:00.0000000

when i connected bussiness intelligence studio

oracle ---->sql staging (db)
when executed dataflow task i got this error



conversation failed because of the data value overflowned by specifed datatype

after that

i have used data conversation Transformation

oracle -->dataconversation--->sql staging (db)

same error getting

pls help me

robvolk
Most Valuable Yak

15732 Posts

Posted - 2012-05-18 : 09:43:30
In order to maintain that datetime precision you'll need to import to a datetime2(7) column. Or you'll need to trim the value to only keep milliseconds if you're importing to datetime.
Go to Top of Page

kond.mohan
Posting Yak Master

213 Posts

Posted - 2012-06-01 : 08:04:59

I HAVE CHANGED MY TABLE DATATYPE IS DATETIME2(7)

ITS WORKING PROPERLY

Thanks

mohan
Go to Top of Page

kond.mohan
Posting Yak Master

213 Posts

Posted - 2012-06-19 : 02:22:39
dear all

they have changed my source column like this way

2012-06-18 05:09:29.0000000

once again i am getting the sameerror

[OLE DB Destination [31]] Error: There was an error with input column "EVENT_TIME" (56) on input "OLE DB Destination Input" (44). The column status returned was: "Conversion failed because the data value overflowed the specified type.".

any body know exlain me
Go to Top of Page

robvolk
Most Valuable Yak

15732 Posts

Posted - 2012-06-19 : 06:31:56
IIRC Oracle datetime can store BCE dates that SQL Server doesn't support. I suggest you check your data for any dates prior to Jan 1 0000, you'll have to filter them out or change them to another value that SQL Server supports.
Go to Top of Page
   

- Advertisement -