RE: session_cached_cursors pros & cons

From: Bobak, Mark <Mark.Bobak_at_il.proquest.com>
Date: Tue, 28 Sep 2004 11:49:49 -0400
Message-ID: <4C9B6FDA0B06FE4DAF5918BBF0AD82CF09660ED9@bosmail00.bos.il.pqe>

Joe,
Go to:
http://www.ixora.com.au/scripts/library.htm and look for the session_cursor_cache.sql script.

-Mark

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Joe Armstrong-Champ Sent: Tuesday, September 28, 2004 11:46 AM To: anjo.kolk_at_oraperf.com
Cc: oracle-l_at_freelists.org
Subject: Re: session_cached_cursors pros & cons

Anjo,

Is there any documentation that can help in deetermining how much bigger =

the shared pool needs to be when using session_cached_cursors?

Thanks.
Joe

Anjo Kolk wrote:

> I haven't read all the replies but one thing to keep in mind with
> session_cached_cursors is that cursors that are normally closed are =
kept
> open and that memory is kept pinned. That means that a larger shared =
pool is
> needed to keep all the 'open' cursors in the shared pool. It is also
> responsible for a larger fragmentation of the shared pool.
>=20
> In fact caching SQL statements increases performance, but could cause =
a
> fragmentation and other shared pool problems.

>=20

> So make sure that your shared pool is big enough.
>=20

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

Received on Tue Sep 28 2004 - 10:45:31 CDT