Consider an Oracle instance that is using Automatic Shared Memory Management…

Consider an Oracle instance that is using Automatic Shared Memory Management. You set some of the System Global Area (SGA) parameters as shown below:
SGA_TARGET = 200 MB
SHARED_POOL_SIZE= 20 MB
DB_KEEP_CACHE_SIZE = 30 MB
Which two statements are correct in this scenario? (Choose two.)

Consider an Oracle instance that is using Automatic Shared Memory Management. You set some of the System Global Area (SGA) parameters as shown below:
SGA_TARGET = 200 MB
SHARED_POOL_SIZE= 20 MB
DB_KEEP_CACHE_SIZE = 30 MB

Which two statements are correct in this scenario? (Choose two.)

A.
Shared pool size will never shrink below 20 MB.

B.
A maximum of 20 MB will be allocated to the shared pool.

C.
230 MB will be allocated among the auto-tuned SGA components.

D.
250 MB will be allocated among the auto-tuned SGA components.

E.
If SGA_TARGET is reduced to 150 MB, then it will not affect the value of the DB_KEEP_CACHE_SIZE parameter.

Explanation:
The main objectives to justify this new functionality are:
* Distribute the available memory depending of the current Workload. The MMAN process will take some regular memory snapshots to evaluate the needs and thereby the dispatching of the usable memory.
* Enhance the memory usage depending of the activity

A note on Oracle metalink, explains way much better, the use of ASMM. The main goal of this document is to show you how to put in place the ASMM facility introduced with Oracle10g, how to configure it, and also some examples on how to monitor its activity.

REF: Metalink Note: 295626.1How To Use Automatic Shared Memory Management (ASMM) In Oracle10g



Leave a Reply 0

Your email address will not be published. Required fields are marked *