Re: SGA sizing in Very Large Memory 6 GB

wchy65_at_yahoo.com (Wade Chy) wrote in message news:<4fad73ef.0311051400.3e64e570_at_posting.google.com>...
> Hi All,
> I am configuring a new Oracle 9.2 server for a Windows 2003. This
> server has 6 GB available memory. I have not worked with VLM before.
> This is a multipurpose database with approximately 20 GB data in it.
> What will the good values for SGA components like
>
> large_pool_size
> java_pool_size
> db_block_buffers
> etc.
> If any body can email me a copy of a sample parameter file with large
> SGA configuration, I would really appreciate it. Also any
> documentation for 4GB RAM TUNING will highly appreciated. Thanx in
> advance.

good news, w2k3 server ships with large memory support. with w2k server, you had to purchase the advanced server edition (read: 2500 USD upcharge).

better news: terminal services on w2k3 support bequeath connections.

recommendation: start without large memory enabled, and tune the application code. this is hardly an original idea, it is echoed here frequently.
Plan on an SGA of no more than 1.7 GB. leave yourself room to crank up your buffer pool(s) by a gig. using an overly large PGA_AGGREGATE_TARGET could cause your usual execution plans to start thinking about hash_joins more frequently that you might like. don't start out with indirect_block_buffers enabled.

if you use a shared pool and java pool of 150 MB each, you'll never have to change them when you apply a patchset. but you'll likely be wasting memory.

how many instances will be active on this server at a time?

check out the book by Hart, Jesse and Sale:

Oracle9i for Windows(R) 2000 Tips & Techniques

as well as the platform-specific release notes, administration guide available at http://otn.oracle.com.

Pd Received on Thu Nov 06 2003 - 00:38:54 CST