SESSION_CACHED_CURSORS
- From: "DBA Deepak" <oracle.tutorials@xxxxxxxxx>
- To: oracle-l <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 30 Aug 2007 23:11:32 +0530
Hi All,
Have a doubt on the SESSION_CACHED_CURSORS parameter. If we set this
parameter to some higher value is there a chance that the shared pool will
get fragmented because of this parameter setting? If yes, then am just
curious to know how?
Some articles say if we have a fragmented shared pool then we may consider
decreasing this parameter value. In this case why Oracle will not be able to
free-up the memory occupied by the cached cursors when space is required in
the shared pool for incoming SQLs.
--
Regards,
Deepak
Oracle DBA
- Follow-Ups:
- Re: SESSION_CACHED_CURSORS
- From: LS Cheng
- Re: SESSION_CACHED_CURSORS
- From: Alberto Dell'Era
Other related posts:
- » SESSION_CACHED_CURSORS
- » RE: SESSION_CACHED_CURSORS
- » RE: SESSION_CACHED_CURSORS
- » Re: SESSION_CACHED_CURSORS
- » SESSION_CACHED_CURSORS
- » Re: SESSION_CACHED_CURSORS
- » Re: SESSION_CACHED_CURSORS
- » Re: SESSION_CACHED_CURSORS
- » Re: SESSION_CACHED_CURSORS
- » Re: SESSION_CACHED_CURSORS
- » Re: SESSION_CACHED_CURSORS
- Re: SESSION_CACHED_CURSORS
- From: LS Cheng
- Re: SESSION_CACHED_CURSORS
- From: Alberto Dell'Era