Re: Oracle.exe Process Dumps Memory

From: Niall Litchfield <niall.litchfield_at_gmail.com>
Date: Tue, 17 Feb 2009 08:05:58 +0000
Message-ID: <7765c8970902170005y15fd997fpa600e530498a67a_at_mail.gmail.com>



From an operating system level you should replace task manger with procexp from sysinternals this will give you thread level views of the resource usage. You can the the thread to the spid in v$process. I'd expect ash to be helpful if you have licensed it. You should also look at the pga usage and or java memory usage if you have any java in the db

On 2/17/09, Nancy Iles <nancy_iles_at_hotmail.com> wrote:
>
> We have Oracle RAC with 5 nodes on Windows 2003 R2 SP2 with database
> 10.2.0.3. On one node we have a problem with periodic concurrency waits.
>
> In Task Manager We see the oracle.exe process growing to 6 to 8 GB and then
> suddenly the Oracle.exe process shrinks to 800 Meg of memory. When the
> memory shrinks, we cannot get a response back from the server for a few
> seconds and in GRID we see a concurrency spike for 3-5 minutes. We also see
> a spike in the swap utilization percentage at the same time as the memory
> dump. Before and after the dump, queries of the database memory show that
> the processes have the same amount of memory consumed. Our theory is that
> the memory for the oracle. exe process is being dumpted to the swap file. We
> have 16RB of RAM and the max memory used is 12GB.
>
> Has anyone run into this issue before or have any ideas how to find the
> cause of the memory shrinking suddenly?
>
> With Regards,
>
> Nancy Iles
> Omni Hotels
> _________________________________________________________________
> See how Windows connects the people, information, and fun that are part of
> your life.
> http://clk.atdmt.com/MRT/go/msnnkwxp1020093175mrt/direct/01/--
> http://www.freelists.org/webpage/oracle-l
>
>
>

-- 
Sent from Google Mail for mobile | mobile.google.com

Niall Litchfield
Oracle DBA
http://www.orawin.info
--
http://www.freelists.org/webpage/oracle-l
Received on Tue Feb 17 2009 - 02:05:58 CST

Original text of this message