Re: PGA_AGGREGATE_TARGET, AUTO PGA TARGET and WORKAREA_SIZE_POLICY

From: Ram Raman <veeeraman_at_gmail.com>
Date: Mon, 9 Oct 2017 13:30:01 -0500
Message-ID: <CAHSa0M0N2ZmNyfSapnGqH+j9Y-+gB7Ff3vizRtB1jxGR+Mc1sg_at_mail.gmail.com>



Thanks, I did not realize that SYS' processes are exempted from that limit. So, it is still possible for the usage to exceed PAL, even in 12c.

Can someone explain what is "most untunable memory" ?

On Fri, Oct 6, 2017 at 5:57 PM, Mladen Gogala <gogala.mladen_at_gmail.com> wrote:

> Hi Ravi,
>
> I know that this is unexpected, but Oracle actually puts the documentation
> on the Internet for free. The first thing I would try is this:
>
> https://docs.oracle.com/database/121/REFRN/GUID-E364D0E5-19F2-4081-B55E-
> 131DF09CFDB3.htm#REFRN10328
>
> This document has a section with the title "What happens when
> PGA_AGGREGATE_LIMIT is exceeded". I will not ruin you the pleasure of
> reading the documentation by telling you the ending.
>
> Regards
>
> On 10/06/2017 06:05 PM, Ravi Teja Bellamkonda wrote:
>
> It would be really helpful if someone can throw some light on this. I
> understand that workarea_size_policy parameter set to auto is related to
> this. But wanted to confirm that PGA used actually crosses the
> PGA_AGGREGATE_LIMIT. Is there any documentation which states that
> PGA_AGGREGATE_LIMIT is a soft limit.
>
> It would be very helpful, if someone can clarify.
>
> --
> Thanks & Regards,
> Ravi Teja
>
>
> --
> Mladen Gogala
> Oracle DBA
> Tel: (347) 321-1217
>
>

--

--
http://www.freelists.org/webpage/oracle-l
Received on Mon Oct 09 2017 - 20:30:01 CEST

Original text of this message