Inserted value too large for column, row rejected.

[kjaouhari]

Hello DSxians !

I run a simple job wih a propagate transformer between 2 oracle tables.
The tables are similar this is why I don't understand how can I get this error message :
At row 1638, link "DSLink11"
Inserted value too large for column, row rejected.

do you have an idea ?

[ray.wurlod]

Example: your column is Char(12) and your data length is greater than 12.
Example: your column is Number(7) and your data value contains more than 7 digits.

[chulett]

And the problem is you don't get a clue from Oracle which field is the problem... you get to figure that out all on your lonesome.

[Nageshsunkoji]

And the problem is you don't get a clue from Oracle which field is the problem... you get to figure that out all on your lonesome.

Hi,

This is purely data problem. As craig suggested, you have to dig yourself into the data, there is no choice to identify it. Just check the 1638 row for all the data as error suggested.

[DSguru2B]

Well just go to the transformer, look the bottom half where the metadata is visible. Examine both input and output visually. You will be able to see which column has a bigger length and is being mapped to a column with lesses length.

[ray.wurlod]

Maybe, but DataStage (in server jobs) does not enforce things like maximum length for VarChar, so it doesn't bite till you get to the INSERT/UPDATE statement.

[chulett]

Right, it's not about the metadata but the actual contents of the field.

[kjaouhari]

thanks, i've checked the metadata input and output but it seems to be ok. (they are similar) . I let you know when I will check data directly.

[DSguru2B]

Right, it's not about the metadata but the actual contents of the field.

O boy. Good luck on that then.
I, once had that problem. But I could tell by looking at the source and target length. But then again, I guess, I was just lucky.