Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!drn.maxwell.syr.edu!news.maxwell.syr.edu!news2.telebyte.nl!border2.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!fu-berlin.de!uni-berlin.de!not-for-mail From: Chuck Newsgroups: comp.databases.oracle.server Subject: Re: MTS and Memory Date: 9 Sep 2004 19:03:55 GMT Lines: 23 Message-ID: References: X-Trace: news.uni-berlin.de UwjZw3ISP1Hs9sy7juZ//QNoFUMpF+5MlMLBZ91bD/QOAX3jk= User-Agent: Xnews/5.04.25 Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:224604 Sybrand Bakker wrote in news:mp41k0pjds927314t0o7ij6l3n02ot2cdk@4ax.com: > On 9 Sep 2004 10:03:55 -0700, "Dave" 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. 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. 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. -- Chuck Remove "_nospam" to reply by email