Re: ASMM experiences

"hpuxrac" <johnbhurley_at_sbcglobal.net> wrote in message news:1192108831.427856.221500_at_50g2000hsm.googlegroups.com...
> Fair enough but there's a middle ground that many people are
> considering. Allow oracle "some degree" of moving memory around but
> set minimum sizes for shared_pool, buffer pools etc so that oracle
> cannot force certain memory areas to go below those minimum sizes.
>
> In effect you constrain ASMM so that it only has a "reasonable
> amount" ( whatever that means in your environment ) of memory to add
> or subtract pool definitions with.
>
> In the configuration you describe though it would not probably be
> worthwhile to implement like that since the shared pool is likely to
> get all of that "reasonable amount" anyway.
>

There was an interesting range of comments on

    http://jonathanlewis.wordpress.com/2006/12/04/resizing-the-sga/

that tend to agree with your view. It's okay to let it be automatic, just so long as it's reasonably constrained. (Getting the correct value for "reasonably" is the difficult bit).

-- 
Regards

Jonathan Lewis
http://jonathanlewis.wordpress.com

Author: Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html

The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html