Escolar Documentos
Profissional Documentos
Cultura Documentos
MEMORY_TARGET is a database initialization parameter (introduced in Oracle 11g) that can be used for automatic PGA and SGA memory sizing.
Parameter description:
MEMORY_TARGET
Property
Parameter type
Syntax
Default value
Modifiable
Range of value
Basic
Description
Big integer
MEMORY_TARGET = integer [K | M | G]
0
ALTER SYSTEM
152 MB to MEMORY_MAX_TARGET
No
By using one parameter we don't need to use all other SGA and PGA parameters like.
DB_CACHE_SIZE
SHARED_POOL_SIZE
LARGE_POOL_SIZE
JAVA_POOL_SIZE
PGA_AGGREGATE_TARGET
Four most commonly configured components are automatically sized:
Shared Pool
Large Pool
Java Pool
Pga_Aggregate_Target
The New view V$MEMORY_DYNAMIC_COMPONENTS shows the current sizes of all dynamically tuned memory components, including the total sizes of the
SGA and instance PGA.
750
1000
1250
1500
1750
2000
8 rows selected.
[edit]Enable
.75
1
1.25
1.5
1.75
2
173
173
173
173
173
173
1
1
1
1
1
1
1
1
1
1
1
1
MEMORY_TARGET
VALUE
-------------0
VALUE
-------------1500M
VALUE
-------------1000M
Now our automatic tuning for both SGA and PGA started by using the above parameter. We can increase the value of MEMORY_TARGET parameter
to MEMORY_MAX_TARGET, if we will try to increase it more from the size of max parameter it will throw error.
[edit]Resize
MEMORY_TARGET
MEMORY_TARGET is dynamic
So to prevent from this error we should increase our MEMORY_MAX_TARGET parameter to avoid the above error. we can check which parameter is static and
which is dynamic by querying v$parameter view.
SQL>select name,isses_modifiable,issys_modifiable,isinstance_modifiable
from v$parameter where name like 'memory_max_target'
NAME
ISSES_MO ISSYS_MO ISINSTAN
---------------------- -------- -------memory_max_target
FALSE
FALSE
FALSE
MEMORY_TARGET
We can disable automatic SGA and PGA tuning by setting MEMORY_TARGET parameter value to 0.
VALUE
----------------0
1440
0
0
2000M
0
944M
656M
Now, Oracle will only tune SGA automatically and we have to tune PGA manually.