data length problem
Moderators: chulett, rschirm, roy
data length problem
hi friends,
i have a parallel job in which for a given column target data length is less then the source data length, both the column are of varchar type. when i am running the job the job is getting aborted ... with error...
sqlcode is: -12899
esql complaint: ORA-12899: value too large for column
i suppose it should not be the scenario.here only the record which is greater then the size should get rejected but the job should finish successfully.
Please look and advice me .. wht should to do make the job rejecting records not to get aborted.
i have a parallel job in which for a given column target data length is less then the source data length, both the column are of varchar type. when i am running the job the job is getting aborted ... with error...
sqlcode is: -12899
esql complaint: ORA-12899: value too large for column
i suppose it should not be the scenario.here only the record which is greater then the size should get rejected but the job should finish successfully.
Please look and advice me .. wht should to do make the job rejecting records not to get aborted.
If the source data is larger than the target column size, you should handle that in the job, either by logically rejecting it via a size check or substringing the data to fit. Oracle will abort if you don't, as you've seen.
Last edited by chulett on Fri Feb 05, 2010 9:05 am, edited 1 time in total.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
but the scene is , why the job is getting aborted ?
because in other cases like ora 1403 error of having duplicates on key or ora 1400 null insert error in keys job finishes smoothly without any aborts , why its happening in this case.
friends its a strange way of dealing data by Data Stage or may be i am wrong.
please suggest me to complete the job without the aborts.
i will be thankful to you friends.
because in other cases like ora 1403 error of having duplicates on key or ora 1400 null insert error in keys job finishes smoothly without any aborts , why its happening in this case.
friends its a strange way of dealing data by Data Stage or may be i am wrong.
please suggest me to complete the job without the aborts.
i will be thankful to you friends.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
CHECK the data before you send it to Oracle.
As you have already been advised.
If you don't send erroneous data, then the server will have nothing to complain about.
In my opinion, jobs should abort if there is an unresolvable data anomaly.
As you have already been advised.
If you don't send erroneous data, then the server will have nothing to complain about.
In my opinion, jobs should abort if there is an unresolvable data anomaly.
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You have seen the full suggestion, all you missed were a handful of words unrelated to the actual solution so I've unmarked it.hellboy wrote:any way i am not the premium member so i can't see the full suggestion given by you...
Regardless, seriously consider a premium membership, there's way too much help and useful information here to not take full advantage of and to help support this site.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers