Re: SGA_MAX_SIZE vs. SGA_TARGET

sga_max_size has only sense in Solaris because DISM in Solaris allocates only the used memory (sga_target) but other platforms has such feature, IMHO sga_max_size is not useful since 10g, if you see someone set sga_max_size larger than sga_target in non solaris platform I would question if he knows what he is doing (I see many unfortunately)

thanks

On Sat, Sep 5, 2015 at 7:50 PM, Dba DBA <oracledbaquestions_at_gmail.com> wrote:

> yeah this is old. I know its on the web. However, the responses I see are
> not to the question I have.
>
> What is the point to having two parameters? If SGA_MAX_SIZE reserves
> memory for oracle as an upper bound, but would I want to be able to raise
> and lower SGA_TARGET? What do I do with the 'spare memory'.
> PGA_AGGREGATE_TARGET is separate and not taken from memory reserved with
> SGA_MAX_SIZE
>
> db_cache,shared_pool, large_pool,streams, java, etc... all come out of
> SGA_TARGET. So what is the point to this? I am missing something.
>
> I have I have 20 GB SGA_MAX_SIZE and a 10 GB SGA_TARGET. What is oracle
> doing with the other 10 GB?
>
>

--
http://www.freelists.org/webpage/oracle-l