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 Error Code 0xC0209084

Author  Topic 

jim_jim
Constraint Violating Yak Guru

306 Posts

Posted - 2011-03-11 : 12:57:43
Iam trying to import data from 6 differant flat files using for each container along with data flow task and get the below error.

The column that is erroring out from the error message is a Database timstamp feild.

Please let me know what am i doing incorrectly.This has been a pain from yesterday


Complete Error Message
[Flat File Source [282]] Error: Data conversion failed. The data conversion for column "OED" returned status value 2 and status text "The value could not be converted because of a potential loss of data.".
DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "output column "OED" (315)" failed because error code 0xC0209084 occurred, and the error row disposition on "output column "OED" (315)" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure.

jim_jim
Constraint Violating Yak Guru

306 Posts

Posted - 2011-03-11 : 13:43:03
I am able to load the flat files after ignoring the date column that is causing the error.
When I see the data in the database I see the date column is empty

Is there any problem with the data?
Go to Top of Page

jscot
Posting Yak Master

106 Posts

Posted - 2011-03-11 : 21:30:09
jim what is the field that giving you problem? date or text column?
Go to Top of Page

jim_jim
Constraint Violating Yak Guru

306 Posts

Posted - 2011-03-16 : 09:09:54
Date column is the one that has been giving the problem
I loaded the data ignoring the failure on this column and saw only 100 rows of the date column were loaded and the remaining are null
Go to Top of Page

jim_jim
Constraint Violating Yak Guru

306 Posts

Posted - 2011-03-17 : 13:40:47
Iam still searching a way to fix this issue and found this MSDN page.It says this is a bug and will be fixed after the installation of Cumulative Update 5 hotfix.

Any one has any suggestions?
Go to Top of Page
   

- Advertisement -