Oracle Troubleshooting: How to read Oracle ERRORSTACK output?!

February 14th, 2010
Goto comments Leave a comment

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:

  1. Reading the current executing SQL statement text from errorstack trace
  2. Reading the current executing PL/SQL package and PL/SQL source code line number from errorstack trace
  3. Reading the current bind variable values from errostack trace
  4. 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 !!! ;-)

  • Share/Bookmark

Tanel Poder
Administration, Cool stuff, Internals, Oracle, Troubleshooting, Tuning

  1. Trackbacks

  2. No trackbacks yet.

  1. Comments

  2. Martin Decker
    February 15th, 2010 at 03:41 | #1
    Reply | Quote

    Hi Tanel,

    great article. Just a small typo: it´s v$sql_bind_capture instead of v$sql_plan_capture.

    Looking forward to reading more great stuff on e2sn…

    Regards,
    Martin

  3. Tanel Poder
    February 15th, 2010 at 06:26 | #2
    Reply | Quote

    @Martin Decker
    Hi Martin,

    Thanks, the typo is fixed now.

  4. Chris Neumueller
    February 15th, 2010 at 06:55 | #3
    Reply | Quote

    Hi Tanel!

    Thanks for a very interesting read. I found another typo: x$klgob should be replaced with x$kglob.

    Regards,
    Chris

  5. Tanel Poder
    February 15th, 2010 at 22:08 | #4
    Reply | Quote

    @Chris Neumueller

    Hi Chris, thanks, typo fixed!

  6. Maxx
    February 16th, 2010 at 14:11 | #5
    Reply | Quote

    Hi Tanel, Do you have a RSS feed setup for the new website ??

  7. Tanel Poder
    February 17th, 2010 at 08:52 | #6
    Reply | Quote

    @Maxx
    Hi Maxx,

    I’m still working on the best solution, I need to test out few things before I can publish this. Basically people need to join the site with their google account… stay tuned!:)

  8. Giridhar Kodakalla
    March 28th, 2010 at 05:36 | #7
    Reply | Quote

    Are there any occassions where the “Current SQL Statement for this Session” in the trace file will be different than whatever is being found from the PL/SQL code (if the sql is from a pl/sql program) which you demonstrated in “Reading the current executing PL/SQL package and PL/SQL source code line number from errorstack trace” by querying DBA_SOURCE?

    If yes, would you please let us know.

    Thanks,
    Giridhar Kodakalla.

  9. Tanel Poder
    March 28th, 2010 at 11:51 | #8
    Reply | Quote

    @Giridhar Kodakalla
    Well, if the SQL you fire from your PL/SQL causes some other SQL to fire recursively (triggers, auditing, recursive data dictionary queries) then you may see other SQL pop up there if you take the errorstack dump when the recursive SQL happens to be executing.