Re: High shared pool usage

From: Tanel Poder <tanel_at_tanelpoder.com>
Date: Wed, 28 Sep 2011 01:36:48 +0300
Message-ID: <CAMHX9J+aFCyw3bwy7DBoD9hfKpOhUn8-Yhouv1BLXM-3ZRdHxw_at_mail.gmail.com>

Yep, I've explained it in the blog entry ... It's because you can't just take away a whole granule from shared pool *if* it still has pinned objects in it. And some objects may stay pinned "forever". That's why in 10.1 you couldn't always shrink shared pool... this KGH NO ACCESS magic wasn't implemented yet ...

--
Tanel Poder
Expert Oracle Exadata book:
http://www.apress.com/9781430233923



On Wed, Sep 28, 2011 at 1:35 AM, D'Hooge Freek <Freek.DHooge_at_uptime.be>wrote:



> Tanel,

>

> Is the "KGH NO ACCESS" component, memory that is entirely used for buffer

> cache or is it the total of the mixed granules (partly containing buffer

> cache, partly containing shared pool stuff)?

>

> Is it normal that the ASMM manager could not free up so many granules when

> the buffer cache had to grow?

>

>

>



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

Received on Tue Sep 27 2011 - 17:36:48 CDT