Conversion error in SSIS 2008

pvsbandi
pvsbandi used Ask the Experts™
on
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
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.". 

Open in new window


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?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
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?

Author

Commented:
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

Commented:
Try change this to "Unicode string[DT_WSTR]"
11/26 Forrester Webinar: Savings for Enterprise

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.

Author

Commented:
Unicode never worked. That's why we had to add a data conversion transform and change it to DT_STR.

Commented:
IC. Are you sure that is the only colum which is giving problem?
Commented:
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' and change the value to 'RD_IgnoreFailure'.

Author

Commented:
Thank you! This worked fine.
I'm able to load the data by probably not loading the bad data.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial