About Dynamic SGA Sizing (Doc ID 266702.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 9.0.1.4 to 9.2.0.5 [Release 9.0.1 to 9.2]
Information in this document applies to any platform.

Goal

Introduce basic concepts associated with dynamic SGA tuning (in Oracle 9i).

NOTE:
The information in this note is originally meant for Oracle 9i where the dynamic SGA resizing is limited.
The dynamic resizing of shared_pool_size was introduced in 9iR1, for large_pool_size in 9iR2 and for java_pool_size in 10gR1.
However, the basic information is essentially also applicable to Oracle 10g and 11g when no Automatic Shared Memory Management (10g: ASMM) or Automatic Memory Management (11g: AMM) is used.
In case ASMM or AMM is used, the pool sizes need to be established differently, e.g. using parameters sga_target or memory_target and active values for pool sizes using underscore parameters like "__shared_pool_size". Normal user defined pool sizes, e.g. shared_pool_size can still be set and function as a minimum value.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms