This content has been marked as final. Show 3 replies
In 10.2 it is difficult to do this. In 11.1 and higher the error number returned by the script is recorded as the error code of the chain step.
thanks for your replay.
Saying difficult you mean impossible ??.
It is difficult because there is no direct supported way to do this. There may be a way to do it though.
The bash script step will log a row to all_scheduler_job_run_details. In additional_info the error code is recorded but it is converted into the system error message corresponding to the message. If you have a list of these system error messages it is easy to convert this back to an error code.
So you could write a pl/sql function that takes a job name and step name, retrieves the last job run row, parses out the system error message, converts it to an error code and returns it.
Then you could use this function in your chain rules (using the full where clause syntax).
Hope this helps,