OPEN_CURSORS and SHARED_POOL_SIZE

SysAdmin of production system has increased shared_pool_size from 20MByte to 110Mbyte to "correct" a shared pool size error. Shortly after, he began seeing "too many open cursors" while trying to login via the front-end
(Silverstream).

RTFM says

To take advantage of additional memory available for shared SQL areas, you may
also need to increase the number of cursors permitted for a session. You can do this
by increasing the value of the initialization parameter OPEN_CURSORS.

But there's no causal relationship between increasing shared_pool_size and the open_cursors error, is there?

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Kirsch, Walter J (Northrop Grumman)
  INET: walter.kirsch-eds_at_eds.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L


(or the name of mailing list you want to be removed from).  You may


also send the HELP command for other information (like subscribing).