July 3, 2008 at 6:14 am
Hi all!
I am getting this error, when I try to insert data in OLEDB destination:
[OLE DB Destination [4316]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "The statement has been terminated.". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "String or binary data would be truncated.".
Any ideas what may be the problem?
Thanks!
July 3, 2008 at 7:51 am
ivanaperic (7/3/2008)
Hi all!I am getting this error, when I try to insert data in OLEDB destination:
[OLE DB Destination [4316]] Error: SSIS Error Code Hresult: 0x80004005 Description: "String or binary data would be truncated.".
Any ideas what may be the problem?
Thanks!
Hi,
Check the datatypes and Column sizes are correct or not. This type of error came for me also when I created SSIS package. This error occurs when the Source column size is bigger than the destination column size.
Thank You
July 4, 2008 at 1:43 am
Thanx for reply!
I have checked the data, and it's ok... Something else must be the problem...
July 4, 2008 at 5:17 am
If you tell what you are doing in SSIS probably I can tell you where is the problem?
What you are doing in SSIS? What is the source and what is the Destination? How do you transfering the data?
Thank You
July 4, 2008 at 5:43 am
I am transferring data from OLE DB source to OLE DB destination, but data is transformed in a component which is developed by the company I work for. This component is mapping columns from source to destination. This is the first time I get an exception like that, it has always worked fine...
I assume that the problem is in data, but not in their types or in length, because correct data goes trough a pipeline... When executing the package, OLE DB source component goes red...
July 4, 2008 at 6:49 am
Hi,
A possible reason for your problem is, transferring text from unicode to non-unicode columns or vice-versa.
Just check the data types in source/destination columns.
July 5, 2008 at 4:02 am
It is possible, I do have varchar type in my source, and dest. column is set to nvarchar... I'll check it on monday 🙂
Thanks!
July 7, 2008 at 2:11 am
No, it's not about varchar/nvarchar...
I've changed data types, but it still doesn't work...
July 7, 2008 at 7:02 am
Problem solved... Some field that I did not use was set to default value of a different type then it supposed to be. And I've been checking only fields that were mapped...
Thanks to all for replies.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply