• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 713
  • Last Modified:

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
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?
0
pvsbandi
Asked:
pvsbandi
  • 4
  • 3
1 Solution
 
sachiekCommented:
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?
0
 
pvsbandiAuthor 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
0
 
sachiekCommented:
Try change this to "Unicode string[DT_WSTR]"
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
pvsbandiAuthor Commented:
Unicode never worked. That's why we had to add a data conversion transform and change it to DT_STR.
0
 
sachiekCommented:
IC. Are you sure that is the only colum which is giving problem?
0
 
sachiekCommented:
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'.
0
 
pvsbandiAuthor Commented:
Thank you! This worked fine.
I'm able to load the data by probably not loading the bad data.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now