Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: large PGA_AGGREGATE_TARGET value problems

Re: large PGA_AGGREGATE_TARGET value problems

From: James McCudden <james.mccudden_at_mckesson.com>
Date: 28 Jan 2004 07:13:36 -0800
Message-ID: <5b8af1c7.0401280713.7e7c5b55@posting.google.com>


Thanks. We have the eager mode swap enabled and have yet to experience this problem. Funny. Are you using OCI calls almost exclusively? If not, maybe there's an issue with the PL/SQL compiler/execution code that is eating the swap.

James

"Richard Foote" <richard.foote_at_bigpond.com> wrote in message news:<o6NRb.32166$Wa.16186_at_news-server.bigpond.net.au>...
> Hi James
>
> We encountered a "bug" (my term, Oracle Support deem it a feature) when
> using P_A_T on Tru64 5.1a whereby massive amounts of swap space was being
> consumed way in excess to the proportion of memory used (approx. 3G PGA used
> up all 30+ G of swap). This impacted CPU and prevented additional logons to
> the DB.
>
> The fix was to set vm-swap-eager in /etc/sysconfigtab to 0 to disable eager
> swap mode and change to lazy (deferred) swap mode. The fault is 1 (eager).
>
> I know you mention having plenty of swap, but originally we thought we had
> plenty as well.
>
> Hope this helps
>
> Richard
Received on Wed Jan 28 2004 - 09:13:36 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US