Someone told me (Oracle Support? Someone here?) that SGH: NO ACCESS is
actually a transfer of data between the buffer cache and the shared pool.
Ours was growing quite large under ASMM. Oracle Support never give us the
skinny on exactly how it was allocated.
On 8/21/06, Allen, Brandon <Brandon.Allen_at_oneneck.com> wrote:
>
> I have an SR open am still working with Oracle Support on getting an
> answer to the same question. Other related problems I'm seeing are:
>
> 1) Large amount of free memory in shared pool, even though cursors are
> getting flushed out of the shared pool very quickly
> 2) Large amount of memory allocated to "KGH: NO ACCESS" in shared pool
>
> I think the solution might be "don't use ASMM", but am waiting for an
> official response.
>
>
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Harvinder Singh
> Sent: Monday, August 21, 2006 8:43 AM
> To: ORACLE-L
> Subject: Automatic Shared Memory question
>
> Hi,
>
> I am checking the Automatic Shared Memory feature and set the following
> 2 parameters in init.ora file and recreate the spfile and restarted the
> oracle:
> sga_max_size=943718400
> sga_target=629145600
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
--
Charles Schultz
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Aug 21 2006 - 12:53:31 CDT
