How can your organization benefit from savings just by replacing your legacy backup solutions with Acronis' #CyberProtection? Join Forrester's Joe Branca and Ryan Davis from Acronis live as they explain how you can too.
Conversion error in SSIS 2008
Hi,
We are migrating data from DB2 UDB 9.7 to MS Sql Server 2008, using SSIS 2008.
Since DB2 is Unicode by default, we had to add a Data Conversion transformation between the DB2 source and the Sql Server target.
Now, we are getting an error message from one of the columns and the error was in the lines of
So, we want to be able to ignore this error and move ahead with the load. But instead of ignoring that one error, it has not loaded anything into the column that was causing this issue. So, when we looked at the target table, there were all NULLs in this column.
Can someone kindly suggest a way to ignore the errors and load the rest of the data in the column, as is?
We are migrating data from DB2 UDB 9.7 to MS Sql Server 2008, using SSIS 2008.
Since DB2 is Unicode by default, we had to add a Data Conversion transformation between the DB2 source and the Sql Server target.
Now, we are getting an error message from one of the columns and the error was in the lines of
Data Conversion Error: Data conversion failed while
converting column xxx to column "Copy of xxx.
The conversion returned status value 4 and status text "
Text was truncated or one or more characters
had no match in the target code page.".
So, we want to be able to ignore this error and move ahead with the load. But instead of ignoring that one error, it has not loaded anything into the column that was causing this issue. So, when we looked at the target table, there were all NULLs in this column.
Can someone kindly suggest a way to ignore the errors and load the rest of the data in the column, as is?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Did you double check colum size? This be a issue too.
Also target code setting sometimes need to changed too.
Is it possible for you to post the screenshot of that data mapping step?
Also target code setting sometimes need to changed too.
Is it possible for you to post the screenshot of that data mapping step?
Sure, please find the conversion screenshot attached. The one highlighted in Black, is the column that has issue.
The length of the column in the source is 50. But even after i changed it to 300 in the data conversion as well as in the target, it is still causing the issue.
Data-Conversion-Screenshot.png
The length of the column in the source is 50. But even after i changed it to 300 in the data conversion as well as in the target, it is still causing the issue.
Data-Conversion-Screenshot.png
Try this option..
go to the properties of the source and select 'show advanced editor'.
go to tab 'input and output properties'
expand the tree node 'oledb souce output'
expand the child node 'output columns'
click on the specific column that gives you trouble.
when you click on the column, the properties of the column will be displayed on the right side. Go to property 'TruncationRowDisposition'
go to the properties of the source and select 'show advanced editor'.
go to tab 'input and output properties'
expand the tree node 'oledb souce output'
expand the child node 'output columns'
click on the specific column that gives you trouble.
when you click on the column, the properties of the column will be displayed on the right side. Go to property 'TruncationRowDisposition'
Premium Content
You need an Expert Office subscription to comment.Start Free Trial