Re: [suse-oracle] Oracle Automatic Memory Management (AMM) on Suse

"Arun Singh" <[email protected]> Tue, 12 Feb 2013 16:22:21 -0700
Newsgroups gmane.linux.suse.oracle.general
Message-ID <[email protected]>
>>> On 2/12/2013 at 1:22 PM, Arturo Gutierrez
<[email protected]> wrote:
> Thanks for the reply.
> However with this setting seems like memory is limited to 7.9 GB.
> =

> Filesystem            Size  Used Avail Use% Mounted on
> udev                  7.9G  2.4M  7.9G   1% /dev
> tmpfs                 7.9G  7.3G  567M  93% /dev/shm
> /dev/sda1             198M  142M   46M  76% /boot
> =

> I can't understand how the Oracle instance start with the setting =

> MEMORY_TARGET=3D12G

Yes, this sounds little weired as you expect MEMORY_TARGET setting less tha=
n /dev/shm.

-Arun

> Version info.
> =

> USE Linux Enterprise Server 11 (x86_64)
> VERSION =3D 11
> PATCHLEVEL =3D 1
> =

> Thanks
> Arturo
> =

> =

> =

> Arun Singh wrote:
>> Hello Arturo,
>>
>> You have to adjust /dev/shm, if you are increasing SGA/PGA size with new=
 RAM =

> (16 -> 64), as Oracle DB is main consumer here.
>>
>> Hope this helps,
>> Arun
>>
>>   =

>>>>> On 2/12/2013 at 10:16 AM, Arturo Gutierrez
>>>>>         =

>> <[email protected]> wrote:
>>   =

>>> Hello everyone,
>>>
>>> I have a question about the automatic memory management introduced in =

>>> Oracle11g R1 called AMM.
>>>
>>> As you know with this memory management is defined by parameter =

>>> MEMORY_TARGET the amounts of memory allocated to SGA / PGA globally, an=
d =

>>> MMAN (Memory Manager) memory transfers from one area to another =

>>> dynamically depending on the workload. In what is so far working on Red =

>>> Hat. Had to define a suitable size in the virtual memory system (tmpfs).
>>> example:
>>> tmpfs / dev / shm tmpfs size =3D 1200m 0 0
>>> To avoid errors like:
>>> SQL> startup
>>> ORA-00845: MEMORY_TARGET not supported on This System
>>>
>>> I observed a Suse system where you are managing a RAC system with a 12G=
B =

>>> MEMORY_TARGET settings and the server has 16GB of RAM.
>>> Normally the size of / dev / shm is half of RAM. So you have to resize =

>>> it in / etc / fstab.
>>> However, in this system is not defined superior value and the instance =

>>> is enabled with this configuration.
>>> I wanted to know if this memory management Suse uses another mechanism?
>>> And that must be taken into account for a RAM upgrade, as this thinking =

>>> go from 16GB to 64GB.
>>>
>>> Many Thanks
>>> Arturo
>>>
>>> -- =

>>>
>>>
>>>
>>>
>>>           Arturo Guti=E9rrez G=F3mez
>>>
>>>
>>>           Formador/Consultor  Tecnologias Oracle
>>>
>>>  =

>>>
>>> Oracle DBA Certified Professional OCP  [7.3-11g]
>>> Oracle Real Application Clusters Certified professional
>>>
>>> Oracle Linux Certified professional
>>>
>>>
>>>            =

>>>
>>>
>>>           Mov=EDl 61 64 70 190
>>>
>>>
>>>            =

>>>
>>> * *
>>>
>>> * *
>>>
>>> * *
>>>
>>> / /
>>>
>>> _______________________________________________
>>> suse-oracle mailing list
>>> [email protected] =

>>> http://listx.novell.com/mailman/listinfo/suse-oracle =

>>>     =

>> _______________________________________________
>> suse-oracle mailing list
>> [email protected] =

>> http://listx.novell.com/mailman/listinfo/suse-oracle =

>>   =

> =

> =

> -- =

> =

> =

> =

> =

>           Arturo Guti=E9rrez G=F3mez
> =

> =

>           Formador/Consultor  Tecnologias Oracle
> =

>  =

> =

> Oracle DBA Certified Professional OCP  [7.3-11g]
> Oracle Real Application Clusters Certified professional
> =

> Oracle Linux Certified professional
> =

> =

>            =

> =

> =

>           Mov=EDl 61 64 70 190
> =

> =

>            =

> =

> * *
> =

> * *
> =

> * *
> =

> / /
_______________________________________________
suse-oracle mailing list
[email protected]
http://listx.novell.com/mailman/listinfo/suse-oracle