DTS

Question

DTS

monika_aug08

Valued Member

Points: 52
More actions
March 26, 2008 at 7:31 am

#124610

i am trying to import data via odbc but i am getting error
[DataReader Source [1482]] Error: The "component "DataReader Source" (1482)" failed because truncation occurred, and the truncation row disposition on "output column "ALLOW_DROP_SHIP" (1684)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic. Login to reply

Loner SSC-Insane Points: 21279 More actions · Answer 1

First of all, are you using SQL Server 2005 ? Then it is called SSIS not DTS anymore. To set up SSIS to load the data is different from DTS.

Please explain more clearly, if you are using SQL Server 2000, maybe you should move this thread under SQL Server 2000.

monika_aug08 Valued Member Points: 52 More actions · Answer 2

monika_aug08

Valued Member

Points: 52

March 26, 2008 at 9:10 am

#794118

Hi,

I am using sqlserver 2005 and SSIS.

Michael Earl-395764 SSC Guru Points: 53873 More actions · Answer 3

Right-click on the source component and open the advanced editor. Go to the inputs and outputs and look at the configuration for the field giving you the error. You have a field length that is too short for the data you are selecting.

My guess is that you modified the query or possibly the schema of your source table at some point and SSIS has failed to correctly get the new meta-data. This could be because you have specified that the component not validate the meta-data, or simply because the ODBC driver is doing a bad job of reporting it. Regardless, if you make the field large enough for the data in the component output, it will fix the issue.

Chinna SSCertifiable Points: 5408 More actions · Answer 4

[DataReader Source [1482]] Error: The "component "DataReader Source" (1482)" failed because truncation occurred, and the truncation row disposition on "output column "ALLOW_DROP_SHIP" (1684)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.

you can solve this problem by just trying to change the data type of the column to nvarchar(max) or could you jus be more detail like sending the column data types so that i can try to figure out which column should be modified

Thanks,
Chinna

Its the Journey which gives you Happiness not the Destination-- Dan Millman

monika_aug08 Valued Member Points: 52 More actions · Answer 5

Hi,

sqlserver datatype is nvarchar(max) and odbc datatype is varchar2.

Chinna SSCertifiable Points: 5408 More actions · Answer 6

try changing the odbc datatype to nrachar(max) or make sure that both the datatype match ...bcoz here when the source column is of lenght 50 and you have a destination column of 45 it shows an error truncation error so have the destination datatype in such a way that the source column will not be truncated and there won tbe any error

Thanks,
Chinna

Its the Journey which gives you Happiness not the Destination-- Dan Millman

monika_aug08 Valued Member Points: 52 More actions · Answer 7

I can't change odbc datatypes (that is varchar2),that is not in my hand,i can do any thing with sqlserevr.

i am trying to import data with the help of these : dataReader source and dataConversion and oldebc data destination.

Chinna SSCertifiable Points: 5408 More actions · Answer 8

hey if that is the case could you please post me some sample rows so that i can have a look and let you know...what ever may be the source you can have data conversion in between and can change it the way we wanted and then map to the dest columns

plz post me some sample rows i shall check it ..

Thanks,
Chinna

Its the Journey which gives you Happiness not the Destination-- Dan Millman

Chinna SSCertifiable Points: 5408 More actions · Answer 9

allow_drop_ship column has the error with truncation ...so if you want to see the rows which makes you cause the error jus go to the source and click on error output and for the column allow_drop_ship under truncatoin jus drop down and change it from fialure ocmponent to redirect row and connect to another flat file destination from source ...connect the red line to the new dest file...and you can see the rows which cause the error and can make changes accrodingly

Thanks,
Chinna

Its the Journey which gives you Happiness not the Destination-- Dan Millman

monika_aug08 Valued Member Points: 52 More actions · Answer 10

Please Elaborate "allow_drop_ship column has the error with truncation ...so if you want to see the rows which makes you cause the error jus go to the source and click on error output and for the column allow_drop_ship under truncatoin jus drop down and change it from fialure ocmponent to redirect row and connect to another flat file destination from source ...connect the red line to the new dest file...and you can see the rows which cause the error and can make changes accrodingly "

here all columns create error which have varchar 2 datatype.

Chinna SSCertifiable Points: 5408 More actions · Answer 11

is allow drop shio the first column of the table and plz post me some sample data.... u can mail me to kurraraghu@gmail.com if it contains something which cannot be posted in the forum...

Thanks,
Chinna

Its the Journey which gives you Happiness not the Destination-- Dan Millman

monika_aug08 Valued Member Points: 52 More actions · Answer 12

Can i import data via odbc to oracle 9i Express Edition via odbc ? if yes ,How?

Chinna SSCertifiable Points: 5408 More actions · Answer 13

try using the same import /export wizard setting the destination to oledb provider for oracle and set the servername ...but i am not sure regd this...jus provide me sample rows so that i shall try ...even i am new to ssis but i have got some knowledge in ssis import...so let me try

Thanks,
Chinna

Its the Journey which gives you Happiness not the Destination-- Dan Millman

Antares686 SSC Guru Points: 125444 More actions · Answer 14

Do you have an existing table you are importing to?

If so it sounds like one of the columns is too short

Ex. Source length is 10 desitnation length is 5.

For the import to work the columns data would have to be truncated. Thus if the source read

"I Want To!"

it would have to truncate to

"I Wan"

to work.

There is a setting to allow the automatic truncation to take place without stopping as an error but is that what you really want to happen.

If not then I would suggest you check each columns length in the source (regardless of datatype, but more for VARCHAR2 columns) and make sure the destination counterpart is wide enough to accetp the entire length of the data from the source column.