如何disable AMM以及ASMM

disable AMM enable ASMM:

将memory_target设置为0

disable AMM  and ASMM:

将memory_target=0 

可参考：

Database Has Memory_Max_Target Set Even if Created with AMM Disabled (Doc ID 1138645.1)

Database Has Memory_Max_Target Set Even if Created with AMM Disabled (Doc ID 1138645.1)

Database Has Memory_Max_Target Set Even if Created with AMM Disabled (Doc ID 1138645.1) To Bottom In this Document Symptoms   Changes   Cause   Solution APPLIES TO: Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.2.0 [Release 11.1 to 11.2] Information in this document applies to any platform. Version: 3-2XSW-27811.1.0.6 to 3-2XSW-72311.2.0.2.0 [Release: 3-2XST-6211.1 to 3-2XST-7311.2] SYMPTOMS When creating a database with DBCA, you explicitly disabled AMM, however when you start the newly created database, you discover there is still a value for the MAX_MEMORY_TARGET. SQL> show parameter memory_max_target  NAME TYPE VALUE  ------------------------------------ ----------- ------------------------------  memory_max_target big integer 30000M CHANGES You created the database with AMM disabled in DBCA. CAUSE This appears to be by design, because, if you want to enable AMM at a later point in time, you can, after startup, dynamically change MEMORY_TARGET to a non-zero value, provided that it does not exceed the value of MEMORY_MAX_TARGET. Therefore if MEMORY_MAX_TARGET is not set initally you would not be able to enable AMM later without a restart. SOLUTION If you want to work around this and ensure that the MEMORY_MAX_TARGET does not get set for whatever reason (it would only matter if MEMORY_TARGET were to get set as well) do the following: 1) Create pfile from the spfile, then remove below lines from pfile and start the instance with pfile and create spfile from this modified pfile and you will see the values 0.  *.memory_max_target=0  *.memory_target=0  2) Create an spfile from the updated pfile.  3) Shutdown Immediate 4) Startup the database with the spfile SQL> show parameter memory  NAME TYPE VALUE  ------------------------------------ ----------- ------------------------------  memory_max_target big integer 0  memory_target big integer 0

Database Has Memory_Max_Target Set Even if Created with AMM Disabled (Doc ID 1138645.1)

Database Has Memory_Max_Target Set Even if Created with AMM Disabled (Doc ID 1138645.1) To Bottom In this Document Symptoms   Changes   Cause   Solution APPLIES TO: Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.2.0 [Release 11.1 to 11.2] Information in this document applies to any platform. Version: 3-2XSW-27811.1.0.6 to 3-2XSW-72311.2.0.2.0 [Release: 3-2XST-6211.1 to 3-2XST-7311.2] SYMPTOMS When creating a database with DBCA, you explicitly disabled AMM, however when you start the newly created database, you discover there is still a value for the MAX_MEMORY_TARGET. SQL> show parameter memory_max_target  NAME TYPE VALUE  ------------------------------------ ----------- ------------------------------  memory_max_target big integer 30000M CHANGES You created the database with AMM disabled in DBCA. CAUSE This appears to be by design, because, if you want to enable AMM at a later point in time, you can, after startup, dynamically change MEMORY_TARGET to a non-zero value, provided that it does not exceed the value of MEMORY_MAX_TARGET. Therefore if MEMORY_MAX_TARGET is not set initally you would not be able to enable AMM later without a restart. SOLUTION If you want to work around this and ensure that the MEMORY_MAX_TARGET does not get set for whatever reason (it would only matter if MEMORY_TARGET were to get set as well) do the following: 1) Create pfile from the spfile, then remove below lines from pfile and start the instance with pfile and create spfile from this modified pfile and you will see the values 0.  *.memory_max_target=0  *.memory_target=0  2) Create an spfile from the updated pfile.  3) Shutdown Immediate 4) Startup the database with the spfile SQL> show parameter memory  NAME TYPE VALUE  ------------------------------------ ----------- ------------------------------  memory_max_target big integer 0  memory_target big integer 0