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

Last updated on OCTOBER 20, 2014

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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms