Unable to get the rejected records from oracle enterprise st
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 50
- Joined: Mon Sep 25, 2006 11:18 pm
- Location: Chennai
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
So now you know what the actual error is. The INSERT statement may suggest which actual CHECK constraint was violated; or there may be more information in the job log or in the Oracle logs.
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:
-
- Participant
- Posts: 50
- Joined: Mon Sep 25, 2006 11:18 pm
- Location: Chennai
- Contact:
rangunathan13,
Let me be a bit more specific about what Craig advised.
The best way to resolve this is to determine what constraints are on the table at a database level and include tests in your job to check each record and route the rejects to a file before they are written to the table.
This would also allow you to set array size back to something more reasonable since you wouldn't need to trap the rejects coming back from the table.
Let me be a bit more specific about what Craig advised.
The best way to resolve this is to determine what constraints are on the table at a database level and include tests in your job to check each record and route the rejects to a file before they are written to the table.
This would also allow you to set array size back to something more reasonable since you wouldn't need to trap the rejects coming back from the table.
Exactly - logical rather than physical rejects. No job should ever knowingly violate a constraint on a table and thus should not only be aware of them all but attempt to ensure compliance with them before sending the record to the database.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers