memory problem

mark m.roth2006 at rcn.com
Mon Oct 13 14:11:10 UTC 2008


lingu wrote:
> Hi,
> 
>   Its clearly indicates you are running out of memory and in the
> syslog its indicating the oracle is the process eating up your memory
> causing the OOM killer to kill that process and retains the operating
> system in normal state.
> 
>  Try to find out the cause of the memory hang, and also check the swap
> space also  during this type of scenario swap space will be fully
> utilized.
> 
>>From system side you have to check top,sar,vmstat for load and i/o and
>  swap in an swap out stats respectively.

Should we assume that the server's already been tuned for Oracle - increasing
shmmem and semaphores? Also, with some versions of Oracle & Linux, there's a
max of virtual memory that Oracle, in its parms, can use - I forget if it's
2.5G or 3.9G
<snip>
	mark




More information about the redhat-list mailing list