Oracle 11g Automatic Memory Management
2013-12-15 00:10
495 查看
In 11g, Oracle database manages the PGA and SGA by default. memory_target decides the overall memory size. In this case, parameters concerning PGA and SGA will be like:
show parameter target;
NAME TYPE VALUE
-------------------------------------------------- ----------- ----------------------------------------------------------------------------------------------------
archive_lag_target integer 0
db_flashback_retention_target integer 1440
fast_start_io_target integer 0
fast_start_mttr_target integer 0
memory_max_target big integer 1584M
memory_target big integer 1584M
parallel_servers_target integer 16
pga_aggregate_target big integer 0
sga_target big integer 0
show parameter workarea;
NAME TYPE VALUE
-------------------------------------------------- ----------- ----------------------------------------------------------------------------------------------------
workarea_size_policy string AUTO
Here, memory_target specifies the Oracle system-wide usable memory. The database tunes memory to the MEMORY_TARGET value, reducing or enlarging the SGA and PGA as needed. However, Total
memory usage can grow beyond the value of MEMORY_TARGET. For example,memory is allocated to PL/SQL tables and varrays regardless of the value of MEMORY_TARGET as long as memory is available at the operating system level.
Even when memory is automatically managed, user still find values assigned to parameter HASH_AREA_SIZE AND SORT_AREA_SIZE, don't get puzzled, this does not mean PGA is manually managed:
NAME TYPE VALUE
-------------------------------------------------- ----------- ----------------------------------------------------------------------------------------------------
bitmap_merge_area_size integer 1048576
create_bitmap_area_size integer 8388608
hash_area_size integer 131072
sort_area_retained_size integer 0
sort_area_size integer 65536
In cases where user needs to maually allocate large amount of memory for hashing and sorting, one can manually manage the PGA by:
alter session set workarea_size_policy=manual;
alter session set hash_area_size=xxxxxxxx;
alter session set sort_area_size=xxxxxxxx;
To change max memory size that Oracle can manage:
show parameter target;
NAME TYPE VALUE
-------------------------------------------------- ----------- ----------------------------------------------------------------------------------------------------
archive_lag_target integer 0
db_flashback_retention_target integer 1440
fast_start_io_target integer 0
fast_start_mttr_target integer 0
memory_max_target big integer 1584M
memory_target big integer 1584M
parallel_servers_target integer 16
pga_aggregate_target big integer 0
sga_target big integer 0
show parameter workarea;
NAME TYPE VALUE
-------------------------------------------------- ----------- ----------------------------------------------------------------------------------------------------
workarea_size_policy string AUTO
Here, memory_target specifies the Oracle system-wide usable memory. The database tunes memory to the MEMORY_TARGET value, reducing or enlarging the SGA and PGA as needed. However, Total
memory usage can grow beyond the value of MEMORY_TARGET. For example,memory is allocated to PL/SQL tables and varrays regardless of the value of MEMORY_TARGET as long as memory is available at the operating system level.
Even when memory is automatically managed, user still find values assigned to parameter HASH_AREA_SIZE AND SORT_AREA_SIZE, don't get puzzled, this does not mean PGA is manually managed:
NAME TYPE VALUE
-------------------------------------------------- ----------- ----------------------------------------------------------------------------------------------------
bitmap_merge_area_size integer 1048576
create_bitmap_area_size integer 8388608
hash_area_size integer 131072
sort_area_retained_size integer 0
sort_area_size integer 65536
In cases where user needs to maually allocate large amount of memory for hashing and sorting, one can manually manage the PGA by:
alter session set workarea_size_policy=manual;
alter session set hash_area_size=xxxxxxxx;
alter session set sort_area_size=xxxxxxxx;
To change max memory size that Oracle can manage:
connect "/as sysdba"; ALTER SYSTEM SET MEMORY_MAX_TARGET = 2048M SCOPE = SPFILE; shutdown immeidate; startup; ALTER SYSTEM SET MEMORY_TARGET = 2048M;
相关文章推荐
- Oracle 11g internals part 1: Automatic Memory Management
- 39 Which statement about Automatic Memory Management with Oracle 11g is true?
- Oracle 11g internals part 1: Automatic Memory Management
- Oracle 11g internals part 1: Automatic Memory Management
- Oracle 11g Release 1 (11.1)——自动存储管理(Automatic Storage Management,ASM)
- memory management in oracle 11G R2
- Oracle 11g ORA-00845: MEMORY_TARGET not supported on this system 说明
- Garbage Collection : Automatic Memory Management in the Microsoft .NET Framework 垃圾回收:在微软NET框架自动内存管理(一)
- Oracle 10g Automatic Storage Management, Part 1: Overview
- 57.Automatic Shared Memory Management is disabled for your database instance. You realize that there
- Oracle 11g新特性:Automatic Diagnostic Repository
- Oracle 11g ORA-00845: MEMORY_TARGET not supported on this system 说明
- Automatic Tuning of Memory Management
- 【2017/4/10】Oracle 11g修改MEMORY_TARGET
- Using Automatic Memory Management
- ORACLE AUTOMATIC STORAGE MANAGEMENT翻译-第二章 ASM instance(1)
- About Oracle Automatic Storage Management
- Oracle 11g ORA-00845: MEMORY_TARGET not supported on this system 报错处理
- Oracle 11g新特性:Automatic Diagnostic Repository
- Oracle 11g自动诊断信息库(Automatic Diagnostic Repository,ADR)概述