asked on 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?
Microsoft SQL Server 2008Microsoft SQL Server 2005Microsoft SQL Server
Last Comment
pvsbandi
ASKER
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 change this to "Unicode string[DT_WSTR]"
ASKER
Unicode never worked. That's why we had to add a data conversion transform and change it to DT_STR.
IC. Are you sure that is the only colum which is giving problem?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thank you! This worked fine.
I'm able to load the data by probably not loading the bad data.
I'm able to load the data by probably not loading the bad data.
Also target code setting sometimes need to changed too.
Is it possible for you to post the screenshot of that data mapping step?