Just a brief addition, run the unix program "top" when the slowdown is
happening. You may see something like your cpu being pinned by any of
various things that could be using it to figure out where stuff is or
should be on your disks. For example, if it is something with fs in
the process name, that would point towards a unix admin issue, if it
has dbw or your instance ID in the name, towards oracle, biod, towards
networking. Or if you are lucky, directly towards the user issue.
Also, as superuser, run swapinfo -at (I think, see your man page) to be
sure you don't have some situation of simply running out of memory and
swapping temporarily. On other platforms, I've seen some settings of
SGA and pga_aggregate_target suddenly use way more memory and start
swapping with just one more session running. Also, check exactly how
much physical memory you have with dmesg.
jg
--
@home.com is bogus.
http://www.aemj.org/cgi/content/abstract/7/12/1341
Received on Mon Jun 27 2005 - 19:48:03 CDT
