We came across situation where we insert / update to the database, at that time if that operation fails we received warning in job execution log. Even though insert / update did not work as expected, DS job finished successfully.
But the negative effect of this is seen in further execution.
What we want to have, is there any kind of message handler or something of that sort, could be used in case if warning is associated with DB related stage ?
Your help is highly appreciated.
Aborting job for warning on the DB insert / update...
Moderators: chulett, rschirm, roy
Aborting job for warning on the DB insert / update...
Thanks with regards,
videsh.
videsh.
-
- Participant
- Posts: 53
- Joined: Fri Apr 18, 2008 8:13 am
- Location: United States
Aborting job for warning on the DB insert / update...
Hi,
If you are using a sequencer to call your job, then you can capture the "WARNING" or "ERROR" message from the DS Director and proceed further with your requirement.
If you are using a sequencer to call your job, then you can capture the "WARNING" or "ERROR" message from the DS Director and proceed further with your requirement.
Regards
Ajay
Ajay
For an DB EE stage, one can attach reject link, which could indicate insert or update SQL failure. On this Reject link, having transformer with constraint abort after 1 rows, would ensure the job gets aborted.
But my problem still not solved, as I cannot use DB EE stage, since the target database I am using is non-partitioned database. And, for API stage I did not find any such option of warning handler or reject link.
Note - I am using DB2 UDB stage.
But my problem still not solved, as I cannot use DB EE stage, since the target database I am using is non-partitioned database. And, for API stage I did not find any such option of warning handler or reject link.
Note - I am using DB2 UDB stage.
Thanks with regards,
videsh.
videsh.