From: <krish.hariharan@quasardb.com>
To: <ujang.jaenudin@gmail.com>, "'oracle-l'" <oracle-l@freelists.org>
References: <3edcb66e0801191636n377eee7ak14bc1f16c559f60f@mail.gmail.com>
Subject: RE: memory problem - oracle 10203 on HPUX
Date: Sat, 19 Jan 2008 18:20:12 -0700
Message-ID: <001a01c85b02$9bec0e60$6401a8c0@BHAIRAVIPC01>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
In-Reply-To: <3edcb66e0801191636n377eee7ak14bc1f16c559f60f@mail.gmail.com>
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-to: krish.hariharan@quasardb.com

Ujang,

Since you mention RAC I suspect this is probably node eviction - the cause
could be cpu utilization (not mentioned) or swap consumption preventing
heart beat messages and consequently resulting in node eviction. Look at the
ocssd.log on the surviving node. How many nodes in your cluster and how busy
are the other nodes (cpu, swap)?

If my understanding of memory usage is correct (as seen in Solaris) the
process maps the SGA and is part of its virtual space and has to reserve
swap proportional to it. I address that using shared servers (MTS) since
only a few processes (in your case 50) need be active and not the 1500 since
you can get away with about 75 shared servers processes (if you are not
already using this capability).

The system logs or the crs/css logs will give you that information. The
other thing to look for is the progressive build up and usage of swap.

Regards,
-Krish
Krish Hariharan
President/Executive Architect, Quasar Database Technologies, LLC
http://www.linkedin.com/in/quasardb

-----Original Message-----
From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org]
On Behalf Of Ujang Jaenudin
Sent: Saturday, January 19, 2008 5:36 PM
To: oracle-l
Subject: memory problem - oracle 10203 on HPUX

folks,

I have a machine (RAC configuration) 10.2.0.4 on HPUX - PARISC.
in a node I have 38GB physical memory, 8 processors.
the machine could not run with asynchronous IO, so I set io slave to
8, and dbwr to 1.

at AWR report, it said that 2GB memory for PGA is enough, and 12GB of
SGA mostly enough.
concurrent user is 1000 until maximum 1500 users connected.
at one time only 30-50 concurrent active with OLTP transaction.

at the OS perspective, it said that mostly 90-100%  memory has been used,
even when high load, 50% of the swap will be used also.
almost every 20 days, the server is rebooted itself,
I think this is due to lack of memory....

why between OS and oracle side there has much big different of memory
usage???


-- 
regards
ujang

"I believe that exchange rate volatility is a major threat to
prosperity in the world today"
Dr. Robert A. Mundell, Nobel Laureate 1999
--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l