Re: Strange error when resizing MEMORY_TARGET

From: Luis Marques <lcarapinha_at_gmail.com>
Date: Wed, 16 Jan 2013 22:57:07 +0000
Message-Id: <A7BD3311-DF83-495F-B41A-A65CA6CC1949_at_gmail.com>



Hi,

8k is the default page size for Solaris 10 (and 11 i think) and Linux is 4k but since nobody here is trying to use hupepages (2GB as example in Solaris) that does make much sense. You can check pagesize -a to see the availability of pagesize in Solaris.

Did you already verified ulimit and project settings for oracle user (shared memory?) Apart from that i have no more value to add at this point :-)

Luis Marques
http://lcmarques.com

On Jan 16, 2013, at 10:17 PM, "CRISLER, JON A" <JC1706_at_att.com> wrote:

> I don't work on Solaris that much, but on Linux this would be mapped against /dev/shm- if /dev/shm was only set to less than 20gb you would run into odd errors. Also, are you trying to mix hugepages and ASMM together? Perhaps there is a limit and its not allowing enough hugepages to be allocated. In linux you cannot mix hugepages and /dev/shm together but I think you can in Solaris.
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of De DBA
> Sent: Tuesday, January 15, 2013 9:01 PM
> To: Oracle Discussion List
> Subject: Re: Strange error when resizing MEMORY_TARGET
>
> Thanks Han.
>
> Unfortunately that did not work. I set all targets to the exact value that they currently occupy, i.e.:
>
> shared pool = 1280M
> large pool = 128M
> streams pool = 128M
> java pool = 256M
>
> pga_aggregate_target = 2496M
> sga_target = 4672M
> db_cache_size = 2752M
>
> Setting memory_target to 16G and even to 20G ( i.e. memory_max_target) still gives the same error "ORA-00846: could not shrink MEMORY_TARGET to specified value" :(
>
> Cheers,
> Tony
>
> On 16/01/13 11:16 AM, Xie, Han wrote:

>> Hi Tony,
>> 
>> Oracle normally gives all new memory to default buffer cache, then dynamically adjust other components later.
>> 
>> What is your shared_pool_size parameter value please?  Is it possible that shared_pool has grown, now oracle wants/needs to shrink it back to its parameter size first before add new memory?
>> 
>> My 2 cents.
>> 
>> Cheers,
>> Han
>> 

> <snip due to overquoting>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
--
http://www.freelists.org/webpage/oracle-l
Received on Wed Jan 16 2013 - 23:57:07 CET

Original text of this message