Re: Strange Memory Information on AWR

From: Andrew Kerber <>
Date: Wed, 23 Oct 2013 09:30:24 -0500
Message-ID: <>

Its beginning to look like Karl Arao nailed it, I think the problem is that they have a scheduled job that has a completely different load profile than the rest of the day, and that requires a dramatically larger pga. Since we allocated large pages for the sga, there is not enough memory for the increasing pga (going from 6g to 20g) so the system is swapping, but for some reason it doesnt show as pga overallocation. I need to figure out why, but I am pretty sure I have identified the problem.

On Wed, Oct 23, 2013 at 9:25 AM, Yong Huang <> wrote:

> Andrew,
> You can also check DBA_HIST_PGASTAT for snapshots of v$pgastat for that
> time period. But that's still system wide information. I always like
> session specific info. So check pga_allocated in v$active_session_history
> for the period if the records are still in there (and if you have the
> license, and are on 11gR2 or up). For session PGA, there's no dba_hist_*
> view that I know of. I collect my own Oracle session and OS process
> specific info, keeping their correlation in mind (see
> Yong Huang
> > Looking at the AWR report, I see PGA memory usage that makes no
> > sense to me. PGA_AGGREGATE_TARGET is set to 6g, but the Memory
> Statistics
> > show a PGA usage of 19G at end, but there is no pga overallocation
> indicated.

Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

Received on Wed Oct 23 2013 - 16:30:24 CEST

Original text of this message