Especially were it to be a windows-based server, there might be totally innocuous looking client applications, including the windows explorer itself, that may leak memory or otherwise do stuff that makes it "appear" as if the reboot is helping. I remember attending a presentation at Openworld some years back where a consultant explained all of the things in windows that could cause problem for oracle and how to turn off as many as you could. _____ From: Jared Still [mailto:jkstill@xxxxxxxxx] Sent: Monday, January 19, 2009 1:55 PM To: mfontana@xxxxxxxxxxx Cc: oracle-l Subject: Re: How to justify a Database Shutdown On Mon, Jan 19, 2009 at 7:57 AM, Michael Fontana <mfontana@xxxxxxxxxxx> wrote: We have seen DB servers running client processes that do leak memory and will benefit from the reboot. So, this may not be a database-specific problem in such a case. My thoughts as well. It could even be some Oracle specific process that is leaking memory. The OCM agents (Oracle Collection Manager) are java based. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist