oracle 11gR1设置AMM管理问题
数据库版本:11.1.0.7.0操纵系统:AIX 6.1
内存参数设置如下:
$ sqlplus /nolog
SQL*Plus: Release 11.1.0.7.0 - Production on Tue Dec 10 12:38:18 2013
Copyright (c) 1982, 2008, Oracle. All rights reserved.
SQL> conn /as sysdba
Connected.
SQL> show parameter memory_target
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
memory_target big integer 110G
SQL> show parameter memory_max_target
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
memory_max_target big integer 110G
SQL> show parameter db_cache_size
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_cache_size big integer 256M
SQL> show parameter shared_pool_size
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
shared_pool_size big integer 0
SQL> show parameter sga_max_size
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
sga_max_size big integer 110G
SQL> show parameter sga_target
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
sga_target big integer 0
SQL> show parameter pga
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
pga_aggregate_target big integer 0
SQL> quit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
$ cat pfile_121012.ora | grep OLAP
OLAP.__db_cache_size=1879048192
OLAP.__java_pool_size=536870912
OLAP.__large_pool_size=536870912
OLAP.__pga_aggregate_target=81335943168
OLAP.__sga_target=43486543872
OLAP.__shared_io_pool_size=0
OLAP.__shared_pool_size=39460012032
OLAP.__streams_pool_size=268435456
为何pga是将近80G的内存,shared_pool也是39G左右,从生成的pfile中看到
如何调整该参数,是因为设置了db_cache_size参数?能否不重启实例进行调整? 显然你的库 可能有大量硬解析,这才是导致shared pool大幅膨胀的原因
你可以设置 db_cache_size的最小大小 Liu Maclean(刘相兵 发表于 2013-12-10 13:48 static/image/common/back.gif
显然你的库 可能有大量硬解析,这才是导致shared pool大幅膨胀的原因
你可以设置 db_cache_size的最小大小 ...
从这边看到的是hard parse不是很多 需要完整的AWR
页:
[1]