Yeap, this one PGA reaching 30GB when developers fire up new reports that's doing tremendous hash joins eating up the server memory causing the kswapd to kick in and swapping at a high rate which translates to CPU wait IO and high load average.. basically killing the server https://lh4.googleusercontent.com/-AB22fuuzLwE/T4b53Ris6QI/AAAAAAAABio/mu_dIx3A3uE/s2048/20120412-template-PGA.png already has instance caging.. but since you are hitting tremendous amount of CPU (wait IO) caused by kswapd that is outside of the Oracle Kernel.. then the instance caging will not be able to control that. On Thu, Apr 12, 2012 at 12:06 PM, kevin jernigan <kevin.jernigan@xxxxxxxxxx>wrote: > You could also use Resource Manager to limit the amount of CPU available > to low priority consumer groups, and also to control or kill runaway > queries: > > http://docs.oracle.com/cd/**E11882_01/server.112/e16638/** > os.htm#PFGRF95151<http://docs.oracle.com/cd/E11882_01/server.112/e16638/os.htm#PFGRF95151> > > -- Karl Arao karlarao.wordpress.com karlarao.tiddlyspot.com -- //www.freelists.org/webpage/oracle-l
