Today I came up with idea to overcome the issue: SQLPlus ERRORLOGGING does not keep error log on rollback. The resolution is to use autonomous transactions to log the errors reported by SQL Plus. What we need to do is to somehow catch the error that is about to be logged and wrap it in an autonomous transaction.
While working heavily on script automation I came across the issue of having an SQLPlus script with optional parameter. Oracle does not allow that by default, and one needs to use a dirty trick to make it work. Vladimir made a great article on how to achieve that. Thank you Vlad, this is really helpful. Vladimir's Diary: On SQL*Plus Defines.
Recently I'm heavily involved in SQL*Plus scripting automation tasks. I must admit that despite all the settings you may set and retrieve with SQL*Plus, it is a real pain to do some good automation with this tool. I'm very glad that Oralce continues to extend Oracle SQL*Plus features, but i must say that it seems like the design details for those new features are not well thought, which gives me a headache when working with this tool and forces me to look for tricks and workarounds for badly designed functionality. In this post I'll write about the downsides of the ERRORLOGGING feature introduced with SQL*Plus 11.1 and above.