Q
Problem solve Get help with specific problems with your technologies, process and projects.

Implementing /3GB and /PAE switches

My SGA quite frequently reaches the 2GB limit. As a workaround we have decided to implement the "/3GB" and the "/PAE" switches in the BOOT.INI file. Are there any aftereffects of this change?

Hi Brian. My database runs on Windows 2000 Advanced Server and the SGA quite frequently reaches the 2GB limit. As a workaround we have decided to implement the "/3GB" and the "/PAE" switches in the BOOT.INI file. Are there any aftereffects of this change? And are there any other things that need to be kept in mind before, while and after implementing this change? Thanks and regards.
If you have access to Metalink, then look for Note 225349.1 for more information with respect to this issue.

One thing to keep in mind is that with both the /PAE and /3GB switches, the server will only be able to access up to 16GB of RAM on the server. This will only be a problem if you have more than 16GB of RAM. If you do have more than 16GB of RAM on your database server, then you may want to consider either /PAE or /3GB, but not both.

The OS account that starts the instance must be granted the 'Lock Pages in Memory' system privilege. Also, when setting /PAE, your cache must be sized with the DB_BLOCK_BUFFERS parameter. And it is a good idea to set USE_INDIRECT_DATA_BUFFERS = TRUE in your INIT.ORA config file.

This was last published in December 2006

Dig Deeper on Oracle database design and architecture

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close