Perhaps you ran out of space on /u01 because your
temporary tablespace is using autoextend files and
a process ran up a massive temp segment with
a couple of hundred thousand extents, and smon has
been trying to clear up the mess ever since.
--
Jonathan Lewis
http://www.jlcomp.demon.co.uk
Host to The Co-Operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
Author of:
Practical Oracle 8i: Building Efficient Databases
Screen saver or Life saver: http://www.ud.com
Use spare CPU to assist in cancer research.
Jason wrote in message <9p5fnc$qjv$1_at_iac5.navix.net>...
>I have an 8.0.5 database running on a two-processor Sun E450. It's been
>running well for a fews years now. A few days ago the db shut down because
>it ran out of space on its /U01 filesystem. We were able to clear up that
>problem at get the db running again, but for the last few days it seems
like
>something is very wrong - the oracle SMON process is constantly running at
>35-45% CPU usage according to CDE's process manager, and everything is now
>running very slowly. Any ideas why SMON would run like this, and what I
can
>do about it?
>
>Thanks,
>Jason
>
>
Received on Sun Sep 30 2001 - 02:34:26 CDT
