SESSION_CACHED_CURSORS

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

Other related posts: