I have written the first article to the troubleshooting section of my new website tech.E2SN.com:
It’s about a very valuable Oracle troubleshooting tool -> ERRORSTACK trace.
I cover 4 frequently asked questions there:
- Reading the current executing SQL statement text from errorstack trace
- Reading the current executing PL/SQL package and PL/SQL source code line number from errorstack trace
- Reading the current bind variable values from errostack trace
- Identifying how much private (UGA) memory a cursor is using
You can read it here:
By the way, if you like my new website, feel free to link to it !!! ;-)
NB! Dates updated: After a 1.5 year break, this year’s only Advanced Oracle Troubleshooting training class (updated with Oracle 12c content) takes place on 14-18 December 2015 and 11-15 January 2016 (I had to reschedule the start from November to December). So sign up now if you want to learn new cool stuff!