Inserted value too large for column, row rejected.
Moderators: chulett, rschirm, roy
Inserted value too large for column, row rejected.
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 ?
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 ?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 222
- Joined: Tue Aug 30, 2005 2:07 am
- Location: pune
- Contact:
Hi,chulett wrote: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.
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.
NageshSunkoji
If you know anything SHARE it.............
If you Don't know anything LEARN it...............
If you know anything SHARE it.............
If you Don't know anything LEARN it...............
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.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
Last edited by ray.wurlod on Wed Nov 22, 2006 11:12 am, edited 1 time in total.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
O boy. Good luck on that then.chulett wrote:Right, it's not about the metadata but the actual contents of the field.
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.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.