MEMORY_MAX_TARGET CAN BE EXCEEDED
Last updated on DECEMBER 24, 2013
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 11.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 24-Dec-2013***
Parameter MEMORY_MAX_TARGET is the maximum limit for parameter MEMORY_TARGET. By setting MEMORY_MAX_TARGET to a value higher than MEMORY_TARGET, MEMORY_TARGET can be dynamically expanded while instance is up and running.
However, the MEMORY_TARGET/MEMORY_MAX_TARGET values can be exceeded in some cases. Total memory can grow beyond the MEMORY_TARGET/MEMORY_MAX_TARGET values. There are some operations that have to be given memory regardless of the memory limits set by MEMORY_TARGET/MEMORY_MAX_TARGET values (assuming that memory is available at the OS level). An example of such a case is when using PL/SQL memory collections such as PL/SQL tables and varrays. In this case PGA may grow more than calculated PGA_AGGREGATE_TARGET and this leads to an amount of memory allocated for the instance (SGA+PGA) more than values set for MEMORY_TARGET or MEMORY_MAX_TARGET.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms