Different Values Found For MEMORY_MAX_TARGET/SGA_MAX_SIZE Between Spfile and V$PARAMETER/Show Parameter
Last updated on FEBRUARY 11, 2015
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 11.2]
Information in this document applies to any platform.
Different values are found for parameters MEMORY_MAX_TARGET and SGA_MAX_SIZE between spfile and v$parameter/show parameter. Those 2 parameters are set explicitly to 0 in spfile, but after database startup, "show parameter" always shows a non-zero value for both parameters, although they are all marked with "not default/not modified/not adjusted" in v$parameter.
The behaviour can be easily reproduced as below:
1. Explicitly set following parameters
4. Repeat with step 1, but change the SGA_MAX_SIZE / MEMORY_MAX_TARGET to values which is smaller than the value from V$PARAMETER in the previous step (let's say, set SGA_MAX_SIZE to 100M and set MEMORY_MAX_TARGER=200M). After recycling the instance, those 2 parameters are also being overridden with the value which is the same as we get from the previous test.
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