Re: PGA on higher version

Thank you.

v$process_memory shows the few top sessions occupying ~80-90MBs of memory each but all of them belong to the category 'Other'. Not seeing any such sql which can be suspected.

So how can we be sure it's just the default organic demand because of the way 19C processes works or we really have some odd sql causing this issue?

We have memory_target and memory_max_target set as '0'. Pga_aggregate_target set as 9GB and pga_aggregate_limit set as 18GB. Number of processes is staying around ~1000. But from DBA_HIST_PGA_STAT it seems we have "total pga allocated" staying almost always around ~15GB, so does it mean that we really need to increase PGA_AGGREgATE_LIMIT here?

On Wed, May 19, 2021 at 4:46 PM Lok P <loknath.73_at_gmail.com> wrote:

> Below does point to the fact that recent Oracle versions need higher PGA.
> But i would say , do check v$process_memory to see if any one odd sql is
> causing this. What are the pga parameters set?
>
> Limiting Process Size with Database Parameter PGA_AGGREGATE_LIMIT (Doc ID
> 1520324.1)
>
> Regards
> Lok
>
> On Wed, May 19, 2021 at 2:30 AM Pap <oracle.developer35_at_gmail.com> wrote:
>
>> We are seeing higher pga_allocated post 19C migration. Experienced
>> Ora-04030 already post migration in many cases.So trying to understand if
>> there is any change in behaviour as compared to 11.2.0.4? And how should we
>> debug and estimate the correct value here?
>>
>> ORA-04030: out of process memory when trying to allocate 248 bytes (KSIPC
>> Top Loca,ksipc pga chnk)
>>
>> Regards
>> Pap
>>
>

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