RE: How to trace PMON

From: Steve Adams <steve.adams_at_ixora.com.au>
Date: Tue, 29 Aug 2000 09:11:24 +1000
Message-Id: <10602.115694@fatcity.com>

Hi Tamara,

If you're comfortably with setting an event in your init.ora file, the following one will cause PMON to write a record of most of what it is doing to its trace file in the background_dump_dest directory.

event = "10246 trace name context forever, level 10"

@ Regards,
@ Steve Adams
@ http://www.ixora.com.au/
@ http://www.christianity.net.au/

@ Going to OpenWorld?
@ Catch the Ixora performance tuning seminar too!
@ See http://www.ixora.com.au/seminars/ for details.

-----Original Message-----
From: Tamara Swilley [mailto:tswilley_at_agency.com] Sent: Tuesday, 29 August 2000 9:23
To: Multiple recipients of list ORACLE-L Subject: PMON Question

I'm on Oracle 8.1.5, Solaris 2.6. Today we had an ORA-0600 error with the following trace file message:

ORA-0600: internal error code, arguments: [plio.c: non-reus], [1], [], [], [], [], [], []

When I did a top command in Unix, I could see that the PMON process was using 24.8% of the CPU. I know that PMON handles failed user processes, cleans up, releases locks, etc. Here's my question... is there away to trace the Unix PID for the PMON process back to a different PID of a failed user job(s) that is/are being 'cleaned up' (in case this happens again tomorrow before Oracle Support can get back to me)? Received on Mon Aug 28 2000 - 18:11:24 CDT