RE: Huge MMON traces - Success
Date: Mon, 17 Nov 2008 11:21:51 -0500
Yong's method was successful as show below, Had to go through 10 databases to find the 3 in question. Volume went from 99% full to 56%. I'll know better next time.
# bdf /ora01
Filesystem kbytes used avail %used Mounted on /dev/vg03/ora01 24576000 21709740 2687817 89% /ora01
# ps -ef | grep -i mmon_XXXXX
oracle 14975 1 0 Jul 29 ? 21:41 ora_mmon_XXXXX oracle 1179 29733 0 10:48:04 pts/ta 0:00 grep -i mmon_XXXXX
# kill -9 14975
# tail -3 alert_XXXXX.log
Mon Nov 17 10:48:33 2008
Restarting dead background process MMON
MMON started with pid=11, OS id=1184
# bdf /ora01
Filesystem kbytes used avail %used Mounted on /dev/vg03/ora01 24576000 16164345 7886625 67% /ora01
Glad to learn something new.
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Tim Gorman
Sent: Saturday, November 15, 2008 1:45 PM To: yong321_at_yahoo.com Cc: oracle-l_at_freelists.org Subject: Re: Huge MMON traces Thanks, Yong! Does MMON get restarted automatically after it iskilled? Or do we have to restart the instance in order for that to happen?
Yong Huang wrote:
Since its development, how about finding out if the entire
instance will shutdown if the MMON process is killed?
Killing MMON doesn't crash instance. Before we migrated most our applications from the unstable Itanium boxes running 10.2.0.2, we periodically killed MMON to release memory. See
Yong HuangReceived on Mon Nov 17 2008 - 10:21:51 CST