It surprised me to learn that by default, on executing multiple commands in EXAPlus, the execution does not stop on error.
I was happily executing batches of code and thinking that everything was fine, as it all executed so quickly, and the last message displaying in the log panel was successful, so therefore, everything worked out…right? WRONG!
My code had a bug in one of the middle scripts, but despite the execution encountering the error, the execution as a whole continued.
Luckily, this was highlighted to me at exaxp16, by one of the support team.
So, here’s how to set the flag, to abort execution on error in EXAPlus:
In EXAPlus, go to SQL > Error Handling > All Errors > Select Abort