PMON - CAUSING CPU 100% [message #55736] |
Thu, 13 February 2003 02:05 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
Jimmy Lim
Messages: 6 Registered: February 2003
|
Junior Member |
|
|
Hi,
I'm running Oracle 8.1.5 on RS6000 machine with 4 CPU. Recently, I found the oracle PMON process is occupying 100% of the CPU time. However, I not sure what is causing it and I could not restart the databases so that it's normal.
Can anyone tell me
1. Under what circumstances can a PMON occupy 100% of the CPU time?
2. Is there any other way to start and stop the PMON process other than re-starting the database?
3. Why an oracle Listener hang?
|
|
|
|
Re: PMON - CAUSING CPU 100% [message #55756 is a reply to message #55742] |
Thu, 13 February 2003 17:31 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
Jimmy Lim
Messages: 6 Registered: February 2003
|
Junior Member |
|
|
I'm not very sure.
However, before "pmon" occupies 100% of the CPU time, the listener hung. I restarted the listener and while monitoring the process, I found pmon at 100%.
Can listener affects pmon?
|
|
|
|
Re: PMON - CAUSING CPU 100% [message #55779 is a reply to message #55736] |
Sat, 15 February 2003 04:05 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) |
sai sreenivas jeedigunta
Messages: 370 Registered: November 2001
|
Senior Member |
|
|
I think u have enabled Audit_Trail=DB in your init.Ora
set that to audit_trail = none. and see if the problem is solved..
generally When logon/logoff is being audited, then when PMON cleans up after a dead process, it tries to insert the audit record for a logoff. This causes PMON to need to allocate a transaction for the audit, update the undo segment header in order to put the transaction into the transaction table, do the write, and update the transaction table to commit the transaction. Any of these operations can run into a resource conflict. Since PMON cannot afford to be blocked, a lock conflict error is signalled if any blocking condition is encountered. This can cause PMON to get into a loop and consuming CPU. This problem can be aggrevated by Oracle7 XA which normally has two or three sessions.
sai
|
|
|