Home » RDBMS Server » Server Administration » Automatic Shared Memory Management - Configuration (10.2.0.3)
Automatic Shared Memory Management - Configuration [message #314076] Tue, 15 April 2008 14:52 Go to next message
barnacle47
Messages: 6
Registered: October 2007
Location: Pennsylvania
Junior Member
Two quick questions about ASMM. We just upgraded to 10.2.0.3 (On Solaris 10), and I set healthy SGA_TARGET and SGA_MAX_SIZE values(1.2 and 1.3TB respectively),and statistics_level=typical. However, I never took the old values for the SGA components out of my init.ora. My understanding is that those values will then be used as "minimum" values within the SGA. Should I just delete the automatically managed components (e.g. shared_pool, java_pool) from the init.ora and let Oracle do what it thinks best regarding the SGA?

The second question is, do you need to use an spfile to enable ASMM? I have read conflicting advice on this one. We currently only use a pfile (init.ora).

Right now, it does not appear that the components are varying in size, and appear to be "static".

COMPONENT CURRSIZE MINSIZE USER_SPECIFIED TYPE
------------------------ ---------- ---------- -------------- -------------
shared pool 496 496 496 STATIC
large pool 160 160 160 STATIC
java pool 160 160 160 STATIC
streams pool 64 64 64 STATIC
DEFAULT buffer cache 336 336 288 INITIALIZING
KEEP buffer cache 0 0 0 STATIC
RECYCLE buffer cache 0 0 0 STATIC
DEFAULT 2K buffer cache 0 0 0 STATIC
DEFAULT 4K buffer cache 0 0 0 STATIC
DEFAULT 8K buffer cache 0 0 0 STATIC
DEFAULT 16K buffer cache 0 0 0 STATIC
DEFAULT 32K buffer cache 0 0 0 STATIC
ASM Buffer Cache 0 0 288 STATIC

13 rows selected.

Any information on how to configure this option properly will be appreciated.
Re: Automatic Shared Memory Management - Configuration [message #314109 is a reply to message #314076] Tue, 15 April 2008 15:46 Go to previous message
rucknrun
Messages: 26
Registered: April 2005
Location: Edgewood, MD
Junior Member

I would remove the the entries for

a. shared_pool_size
b. large_pool_size
c. java_pool_size
d. db_chache_size and/or db_block_buffers
e. streams_pool_size

That way you take better advantage of the automated nature of ASMM.

I am not sure about the spfile vs. pfile question. I recently went through the procedure of migrating databases to ASMM. We use the spfile and it seems to be working fine.

[Updated on: Tue, 15 April 2008 15:47]

Report message to a moderator

Previous Topic: Listner_problem
Next Topic: Invalid Packages After Restarting Instance
Goto Forum:
  


Current Time: Sun Dec 11 04:31:39 CST 2016

Total time taken to generate the page: 0.06018 seconds