Yes, correct. In addition, it's interesting to note that in version < 9.2.0.5, the max dimension of the PL/SQL Cursor Cache was dictated by open_cursors, whose default value is much higher than session_cached_cursors (and which is usually lower even when no set to the default). On 8/31/07, LS Cheng <exriscer@xxxxxxxxx> wrote: > Hi Alberto > > I think I didnt explain poperly. > > I mean > > Version < 9.2.0.5: No fragmentation caused by session_cached_cursors because > it was simply a PGA thing > Version >= 9.2.0.5:Possible fragmentation because PL/SQLCursor Caching is > now controlled by this parameter so the parameter now affects both PGA and > SGA -- Alberto Dell'Era "the more you know, the faster you go" -- //www.freelists.org/webpage/oracle-l