Re: PGA_AGGREGATE_TARGET, AUTO PGA TARGET and WORKAREA_SIZE_POLICY

  • From: Mladen Gogala <gogala.mladen@xxxxxxxxx>
  • To: "Reen, Elizabeth" <elizabeth.reen@xxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 12 Oct 2017 19:58:18 -0400

Interesting. I have good experiences with pooled connections. As for the inactive process killer, I usually do that by setting the resource limit for the idle time, like described here:

https://docs.oracle.com/database/121/SQLRF/statements_6012.htm#SQLRF01310

With the pooled connection, disconnection results in returning the server to the pool. I definitely agree that for OLTP applications, inactive sessions should be killed after relatively short time of inactivity, like 15 minutes or so. Sometimes 3rd party applications are written in such a way that screen forms are populated by using "select for update", which can have interesting consequences if the person operating the session goes to a meeting or takes a lunch break.


On 10/12/2017 03:48 PM, Reen, Elizabeth wrote:

We have tried that and more.  All have had some undesirable side effect.  
Connection pooling got filled up and the world hanged.  Dedicated is the only 
methodology which keeps it manageable. We have an idle process killer.  Some 
days it's very active. Other days are not very active.  It's third party stuff 
so we can't see what they are doing.

--
Mladen Gogala
Oracle DBA
Tel: (347) 321-1217

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


Other related posts: