Comments on: Oracle Troubleshooting: How to read Oracle ERRORSTACK output?!

By: Tanel Poder

Tanel Poder — Sun, 28 Mar 2010 16:51:53 +0000

@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.

By: Giridhar Kodakalla

Giridhar Kodakalla — Sun, 28 Mar 2010 10:36:09 +0000

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.

By: Tanel Poder

Tanel Poder — Wed, 17 Feb 2010 13:52:43 +0000

@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!:)

By: Maxx

Maxx — Tue, 16 Feb 2010 19:11:58 +0000

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

By: Tanel Poder

Tanel Poder — Tue, 16 Feb 2010 03:08:07 +0000

@Chris Neumueller Hi Chris, thanks, typo fixed!

By: Chris Neumueller

Chris Neumueller — Mon, 15 Feb 2010 11:55:40 +0000

Hi Tanel!

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

Regards,
Chris

By: Tanel Poder

Tanel Poder — Mon, 15 Feb 2010 11:26:53 +0000

@Martin Decker Hi Martin, Thanks, the typo is fixed now.

By: Martin Decker

Martin Decker — Mon, 15 Feb 2010 08:41:37 +0000

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