Contextual Guidance at the moment of need helps your employees adopt to new software or processes instantly. Boost knowledge retention and employee engagement step-by-step with one easy solution.
Course Of The Month
5 days, 21 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Conversion error in SSIS 2008
Posted on 2012-12-27
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?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
4-
3
7 Comments
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'
Featured Post
We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
In this article we will learn how to fix “Cannot install SQL Server 2014 Service Pack 2: Unable to install windows installer msi file” error ?
In part one, we reviewed the prerequisites required for installing SQL Server vNext.
In this part we will explore how to install Microsoft's SQL Server on Ubuntu 16.04.
Via a live example, show how to setup several different housekeeping processes for a SQL Server.
Viewers will learn how the fundamental information of how to create a table.
Suggested Courses
Course of the Month5 days, 21 hours left to enroll
705 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.