Re: Maximum size for PGA_AGGREGATE_TARGET

From: Scott Sibert <ssibert_at_gmail.com>
Date: Tue, 19 Jan 2010 08:09:54 -0600
Message-ID: <9a600bbf1001190609n64450448l5c1fb1f75ad94b92_at_mail.gmail.com>

I think you're right about PGA and HugePages. You can't use Automatic Memory Management and have it use HugePages and that would be because the instance can shift memory between the SGA and PGA. It'd be nice if it could use HugePages.
--Scott

On Tue, Jan 19, 2010 at 6:24 AM, Guillermo Alan Bort <cicciuxdba_at_gmail.com>wrote:

> Just a thought, but PGA_AGGREGATE_TARGET is the *target* (not a hard limit)
> for the maximum memory allocated in PGA, that is the sum of each process'
> PGA This being the case, and having the 1.7G limit in most 32bit linux
> kernel (not sure in other unix system) you are only limited by this in each
> process. AFAIK PGA cannot use hugepages.
> On the other hand, on windows, you are limited to 2G on the ENTIRE oracle
> process that is PGA + SGA, unless PAE/AWE is used.
>
> hth
> Alan.-
>
>
> On Tue, Jan 19, 2010 at 8:57 AM, Martin Bach <
> development_at_the-playground.de> wrote:
> [SNIP]
>

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

Received on Tue Jan 19 2010 - 08:09:54 CST