INS-35178错误,AMM及ASMM区别


image遇到这个报错,就使用asmm

一般先装库,再opatch到最新补丁,最后dbca建库,物理内存大于4G不能用AMM只能用ASMM

内存越大,全自动管理就越费劲,出错概率就越高,内存抖动


oracle的内存管理:

9i PGA自动管理SGA手动管理,10g PGA自动管理 SGA自动管理(ASMM 自动共享内存管理),11g PGA SGA统一自动管理(AMM,自动内存管理),12c 18c 19c和11g一样没有变化


11g concepts有如下描述

Memory management involves maintaining optimal sizes for the Oracle instance memory structures as demands on the database change. Oracle Database manages memory based on the settings of memory-related initialization parameters. The basic options for memory management are as follows:

  • Automatic memory management

    You specify the target size for instance memory. The database instance automatically tunes to the target memory size, redistributing memory as needed between the SGA and the instance PGA.

  • Automatic shared memory management

    This management mode is partially automated. You set a target size for the SGA and then have the option of setting an aggregate target size for the PGA or managing PGA work areas individually.

  • Manual memory management

    Instead of setting the total memory size, you set many initialization parameters to manage components of the SGA and instance PGA individually.

If you create a database with Database Configuration Assistant (DBCA) and choose the basic installation option, then automatic memory management is the default.


ASMM是10g引入的技术,实现SGA的自动管理,启用后不再需要为每个内存组件设定值,如果同时启用SGA_TARGET为0表示禁用ASMM,非0值表示启用ASMM,但是在10gR1等早期版本,ASMM不够成熟有较多bug

AMM自动化内存管理是11g引入的技术,实现了PGA和SGA的统一自动管理


由此在11g后,就组合出来5种内存管理形式

  自动内存管理(AMM):memory_target=非0,是自动内存管理,如果初始化参数LOCK_SGA=TRUE,则AMM是不可用的

  自动共享内存管理(ASMM):memory_target=0 且 sga_target=非0的情形下是自动内存管理

  手工共享内存管理:memory_target=0 且 sga_target=0 指定share_pool_size、db_cache_size等sga参数

  自动PGA管理:memory_target=0 且 workarea_size_policy=auto and PGA_AGGREGATE_TARGET=值

  手工PGA管理:memory_target=0 且 workarea_size_policy=manal 然后指定SORT_AREA_SIZE等PGA参数,一般不使用手动管理PGA

posted @ 2019-09-12 10:03 九命猫幺 阅读(...) 评论(...) 编辑 收藏