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! I am running one more Advanced Oracle Troubleshooting training in 2018! You can attend the live online training and can download personal video recordings too. The Part 1 starts on 29th January 2018 - sign up here!