RE: Large PGA for a data warehouse on Windows 2003 advanced server(32 bit)

I don't believe it's true that the /3gb switch can't be used, just that it will 
limit you to 16GB only even if you have > 16gb.  From Metalink Note:225349.1

Enabling support at the OS level:
==================================

    AWE can be enabled at the OS by adding the /PAE switch to the boot.ini 
    as such:

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced 
Server" /PAE

    It IS possible to have BOTH the /PAE and /3GB switch in place on the same
    machine, as such:

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced 
Server" /3GB /PAE

    However, be aware that if BOTH switches are in place, the server will only
    be able to recognize up to 16GB of RAM.  If you are working with a server 
    with more than 16GB of RAM, you will need to choose between the two.




-----Original Message-----
From: Ken Naim [mailto:kennaim@xxxxxxxxx]
Sent: Thursday, July 28, 2005 9:40 AM
To: Allen, Brandon; oracle-l@xxxxxxxxxxxxx
Subject: RE: Large PGA for a data warehouse on Windows 2003 advanced
server(32 bit)


Brandon,

I have read that the /3gb switch cannot be used once the server has greater
than 16gb of ram. I have already set the /pae switch and am using
USE_INDIRECT_DATA_BUFFERS=true and currently have 6gb allocated to
db_block_buffers with good results so far. I have not opened a tar yet as I
was hoping someone already encountered this issue and had a solution. 

Thanks,
Ken

-----Original Message-----
From: Allen, Brandon [mailto:Brandon.Allen@xxxxxxxxxxx] 
Sent: Thursday, July 28, 2005 11:27 AM
To: kennaim@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Large PGA for a data warehouse on Windows 2003 advanced
server(32 bit)

Ken,

See Metalink Note 1036312.6 for info on how to use up to 3GB (set /3GB
switch in your boot.ini) or see note 46001.1 for info on how to use more
than 3GB  (for buffer cache only - you have to set
USE_INDIRECT_DATA_BUFFERS=true, and then use the old, static
db_block_buffers instead of new, dynamic db_cache_size - and can't use
db_cache_advice either).  So, theoretically, I believe you could use 1GB for
Windows, 3GB for your PGA/SGA and then use the remaining 28GB for your
buffer cache.  I don't think there is anyway to allocate 4-6gb for PGA on
Windows, but maybe someone else will have an idea.  Have you opened a TAR?

I've used the 3GB switch a few times with no problems, but have never used
the second method for accessing > 3GB. If you try it, please let me know how
it goes.

Thanks,
Brandon

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On
Behalf Of Ken Naim
Sent: Thursday, July 28, 2005 9:15 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Large PGA for a data warehouse on Windows 2003 advanced server(32
bit)


Dear List,

I am developing a data warehouse using Oracle 10g R1 on Windows 2003
advanced server(32 bit). The server has 32gb of ram and ideally I'd like to
allocate a good portion of it to the pga and not just db block buffers. As I
understand it windows "sees" 4gb of ram, 2gb of which is for windows, 1gb
which is used for db block buffers which can map to higher regions of memory
for larger amounts of db block buffers, leaving only 1gb of memory for the
sga and pga. I'd like to know if there is a way to use more of the ram for
the pga, in the neighborhood of 4-6gb. 

My background is on the unix side, so please keep the switch to linux
comments to a minimum. I do not have a choice in this matter.

Thanks,

Ken Naim

Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions
and other information in this message that do not relate to the official
business of this company shall be understood as neither given nor endorsed
by it.

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

Other related posts: