RE: Memory issue with Oracle 10g database on Sun Server T5140 with Solaris 10
- From: "Mandal, Ashoke" <ashoke.k.mandal@xxxxxxxxxxxxx>
- To: Keith Moore <kmoore@xxxxxxxxxxxx>, oracle-l <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 16 Oct 2008 12:16:54 -0500
Keith,
You are right each thread is counted as one cpu.
We have one T2000 server with Solaris 10 and the cpu_count is 24 and I didn't
have problem in creating 10.2.0.4 database with SGA_TARGET as 256M on this
server.
Where as on T5140 (Solaris 10) with cpu_count 128 I am not able to create a
10.2.0.4 database with SGA_TARGET as 256M. Either I have to set the SGA_TARGET
to 900MB without changing the cpu_count parameter or change cpu_count to 4 and
use SGA_TARGET as 256M.
I can't afford to have 900MB as SGA_TARGET for each of my databases (70+) on
the same server. So my next option is to limit the cpu_count to 4. I am trying
to find out from the list if this is the only option (i.e. cpu_count=4) to
overcome my problem on T5140 server or there is any other recommendation.
Thanks,
Ashoke
-----Original Message-----
From: Keith Moore [mailto:kmoore@xxxxxxxxxxxx]
Sent: Thursday, October 16, 2008 9:32 AM
To: Mandal, Ashoke; oracle-l
Subject: Re: Memory issue with Oracle 10g database on Sun Server T5140 with
Solaris 10
Check the value for the cpu_count initialization parameter. I ran into a
similar problem because some memory parameters are based on a mimum per CPU.
On the Sun Cool Threads servers, Oracle counts each thread as a CPU.
In our case, the cpu_count was 64 for a little T2000 server.
Keith
----- Original Message -----
From: "Mandal, Ashoke" <ashoke.k.mandal@xxxxxxxxxxxxx>
To: "oracle-l" <oracle-l@xxxxxxxxxxxxx>
Sent: Thursday, October 16, 2008 9:16 AM
Subject: Memory issue with Oracle 10g database on Sun Server T5140 with Solaris
10
> Greetings All,
>
> I am trying to create an Oracle 10.2.0.4 database with SGA_TARGET=256M
> on Sun T-5140 server with Solaris 10 but getting the following error
> ORA-00821: Specified value of sga_target 256M is too small, needs to
> be at least 536M
>
> When I increased the SGA_TARGET to 536M and tried creating the
> database then I received the following error:
> ORA-12853: insufficient memory for PX buffers: current 0K, max needed
> 11088K
> ORA-04031: unable to allocate 65560 bytes of shared memory ("large
> pool","unknown object","large pool","PX msg pool")
>
> When I set the large_pool_size to 11088K and tried creating the
> database then I received the following error:
> ORA-00821: Specified value of sga_target 536M is too small, needs to
> be at least 548M
>
> When I increased the SGA_TARGET to 548M and set large_pool_size to
> 11088K then it moves little further but failed again with the following
> errors:
> error 4031 detected in background process
> ORA-04031: unable to allocate 2840 bytes of shared memory ("shared
> pool","unknown object","sga heap(1,1)","KQR XPO"
>
> If I specify the SGA_TARGET as 900M then I was able to create the
> database without any problem. But I am looking for a solution so that
> I can create
> 10.2.0.4 database on this hardware with SGA_TARGET as 256M. T5140
> server has total of 16 CPUs and with 8 threads it has 128 virtual
> CPUs. We have also experimented that if we set the cpu_count to 4 in
> the init.ora then we were able to create the database with SGA_TARGET as 256M.
>
> I am wondering if any of you have experienced such problem and have
> recommendation to this issue as I can't afford to allocate 1GB of SGA
> to each of 70 databases on the same server having only 64GB of RAM.
>
> Thanks,
> Ashoke Mandal
>
>
> [CONFIDENTIALITY AND PRIVACY NOTICE]
>
> Information transmitted by this email is proprietary to Medtronic and
> is intended for use only by the individual or entity to which it is
> addressed, and may contain information that is private, privileged,
> confidential or exempt from disclosure under applicable law. If you
> are not the intended recipient or it appears that this mail has been
> forwarded to you without proper authority, you are notified that any
> use or dissemination of this information in any manner is strictly
> prohibited. In such cases, please delete this mail from your records.
>
> To view this notice in other languages you can either select the
> following link or manually copy and paste the link into the address
> bar of a web
> browser: http://emaildisclaimer.medtronic.com
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
