Re: Using Unix debuggers to attach to Oracle processes

ksudps() prints processtate, it might be worth to start with this one if your system is hung and proceed from there.

Those three functions are the only three which ever should be called directly and only in very extreme circumstances when even connect as sysdba doesn't work. And before resorting to that, a direct attach sga program, dumping v$session_wait should be done before (if not using 10gR2's EM direct attach mode). Several versions of such program are available from internet.

Tanel.

• Original Message ----- From: "Egor Starostin" <egorst_at_gmail.com> To: <sac_at_uillinois.edu> Cc: "oracle-l" <oracle-l_at_freelists.org> Sent: Friday, May 05, 2006 1:55 PM Subject: Re: Using Unix debuggers to attach to Oracle processes

>> Update: Actually, calling ksudss from adb did produce a trace file.
>> Unfortunately, adb never returned control to the shadow process and
>> consequently generated a 16gb trace file (only completed because I
>> bounced the database). That was interesting. I was positive hanganalyze
>> dumps were not that big. =)
> You are right, hanganalyze dumps are not that big. Actually, when you
> call ksudss(), it produces systemstate dump. If you want hanganalyze
> trace, you need to call ksdhng() instead.
>
>
> --
> Egor
> http://www.oracledba.ru
> --
> http://www.freelists.org/webpage/oracle-l
>
>

--
http://www.freelists.org/webpage/oracle-l