Re: session_cached_cursors pros & cons
- From: Joe Armstrong-Champ <joseph.armstrong-champ@xxxxxxxxx>
- To: anjo.kolk@xxxxxxxxxxx
- Date: Tue, 28 Sep 2004 11:45:32 -0400
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.
>
> In fact caching SQL statements increases performance, but could cause a
> fragmentation and other shared pool problems.
>
> So make sure that your shared pool is big enough.
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
