Re: MTS and Memory

From: Howard J. Rogers <hjr_at_dizwell.com>
Date: Fri, 10 Sep 2004 05:23:42 +1000
Message-Id: <4140adc5$0$27888$afc38c87@news.optusnet.com.au>

Chuck wrote:

> Sybrand Bakker <gooiditweg_at_sybrandb.verwijderdit.demon.nl> wrote in
> news:mp41k0pjds927314t0o7ij6l3n02ot2cdk_at_4ax.com:
>

>> On 9 Sep 2004 10:03:55 -0700, "Dave" <david.best_at_gmail.com> wrote:
>> 
>>>Now my question is, since i'm using MTS how far can I bump up my SGA..
>> 
>> first of all: why do you think using MTS  you *should* 'bump the SGA'

>
> Probably because Oracle recommends it with MTS.

It does no such thing.

> Since the UGA is
> allocated primarily out of the large pool, and that is part of the SGA,
> you need to increase the size of the SGA (via the large pool) to handle
> those UGAs.

And where do you think those UGAs were before you implemented a large pool (or before implementing MTS, come to that)?

They were with the PGA, or in the shared pool.

So now they're not and they're in the large pool instead.

So tell me where the memory *increase* is in that, as opposed to the memory re-distribution?

HJR
>
> For the OP, there are other ways to increase the amount of memory Oracle
> can access too but I've never found it necessary. Check metalink document
> 46001.1. It's for Windows NT but holds true for Win2k as well. It details
> how to allow Oracle to access up to 3g of memory.
>
> Remember too that Windows will use 1g itself.
Received on Thu Sep 09 2004 - 14:23:42 CDT