FW: Forcing ASMM component to shrink

Sander,  

See reply of Yasin Baskan. He has answered my concern. That if free memory is not there ie. Its already allocated to some other component, then you will get following error.  

ORA-00384: Insufficient memory to grow cache    

From: Sander Westphal [mailto:sander.westphal_at_gmail.com] Sent: 02 December 2007 09:57
Cc: vishal_at_vishalgupta.co.uk; oracle-l_at_freelists.org; anelson77388_at_gmail.com Subject: Re: Forcing ASMM component to shrink    

I do agree with Allan;

So you can set the lower-limit of the cache size to a higher value if realy needed.

The instance will use your this setting as the lower bound, or the smallest size that

particular area may be.      

Cheers, Sander Westphal

OCP 8i,9i, 10G

and your Dutch colleague.  

On Dec 2, 2007 3:16 AM, Allan Nelson <anelson77388_at_gmail.com> wrote:

You will have to push some of the memory you took away from the shared pool to another memory pool. Shrinks don't do anything if the memory freed is not allocated elsewhere.

Allan  

On Dec 1, 2007 10:59 AM, Vishal Gupta <vishal_at_vishalgupta.co.uk> wrote:

Hi,  

Does anyone know if there is any way to force ASMM memory component to shrink. Eg. Instance has just been bounced and say shared pool is using 1GB and db_cache is using only 100MB. If one wanted to forcibly shrink shared pool without bouncing the instance, is there any way to do this?  

Cheers,

Vishal    

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