Comments on: Advanced Oracle Troubleshooting Guide, Part 2: No magic is needed, systematic approach will do

By: Roman

Roman — Tue, 07 Feb 2012 21:49:25 +0000

Please update link to sw.sql it is brocken on all pages

By: Tanel Poder

Tanel Poder — Tue, 22 Mar 2011 12:03:38 +0000

@cam I started from somewhere too. That's why I put the 2 metalink note references there, they help understanding what these function name prefixes are about, they help to point you in the right direction.

By: cam

cam — Tue, 22 Mar 2011 11:56:52 +0000

Very interesting.. but unless I am armed with your knowledge of Oracle internals I can’t possibly decode that stacktrace and thus arrive at the solution…

By: Patryk

Patryk — Sat, 06 Feb 2010 01:01:37 +0000

Hi Tanel,

I never seen such a deep investigation.
Keep going man.

By: Khalid Azmi

Khalid Azmi — Sat, 09 Jan 2010 07:39:50 +0000

Your blog is just WOW, why didn’t i come across this earlier. I think i read somewhere in your blog that you were planning to write a book but then dropped it :(

By: tanelp

tanelp — Thu, 27 Mar 2008 13:10:41 +0000

Newer versions of HP-UX should have the pstack utility.

Otherwise you should be able to do the same with a debugger like dbx or gdb (whichever is present on your machine).

On which HP-UX version are you?

By: qihua

qihua — Thu, 27 Mar 2008 06:48:37 +0000

how hpux? what kind of tool hpux provided could do the same investigation

By: Advanced Oracle Troubleshooting Guide, Part 3: More adventures in process stack « Tanel Poder’s blog: Core IT for geeks and pros

Wed, 05 Sep 2007 16:50:55 +0000

[...] So, reading the bold sections from bottom up (and using the Metalink note 175982.1 I’ve mentioned earlier) [...]

By: tanelp

tanelp — Sat, 01 Sep 2007 09:13:42 +0000

Yep, Linux /proc filesystem allows you to write a pstack utility reading directly from /proc//mem too, but looks like it’s not written yet :)

By: amit poddar

amit poddar — Fri, 31 Aug 2007 20:45:32 +0000

Linux also has a /proc file system.

Do you know why they chose a intrusive method instead of reading it of from the /proc file system ?