Since no-one's answered this, I'll propose my theory,
although I'm not sure it's right.
The session_cached_cursors is just an array in the
UGA (session memory), which means it will be stored
in the SGA when using the multi-threaded server.
The function of the cache is to maintain pointers
into
Hi Jonathan,
It actually caches the whole instantiation object, not the just the library cache lock
(which serves as the pointer to
the shared cursor handle in the SGA). That means that it not only saves locating and
locking the library cache object
again, but it also saves extra instantiation
