This content has been marked as final. Show 4 replies
The end action is the right way to stop a chain.
If a step of the chain throws an error the chain does not stop, you still need to have a rule which calls an END action.
If you are calling the END action but your chain still requires another run to completely stop, you may be running into a known bug which has been fixed in later versions. If this is the case, oracle support should have access to a one-off fix for this issue for your version or you can update to a later version.
Thanks for replying. As I said, I am trapping the failure and calling an "End Action" To be specific, the action is "END 100" - not sure where this came from or why the 100.
Is that the "End Action" to which you refer?
If so, then it does appear that I am hitting that bug. I don't suppose you have any reference for the bug # do you?
Yes that is the end action I am talking about. So it looks as if you are doing it right.
Are you using run_job to run the job ?
The bug I was referring to mostly occurs when run_job is used.
It is tracked internally by bug #5705385. It is fixed in 10.2.0.5 and 11.1.0 . An official patch seems to be available for 10.2.0.3 .
It does have the same symptom though
" The job stops running as expected but, the chain itself, for some reason, is still in a running state. On the next run, the chain will stop (basically, the job will start and then immediately stop). After this, the job can be run normally."