Re: ORA-04031 and shared pool

Things are aged of the shared pool. In fact, by the time you get the 4031, oracle has already done everything it can to flush out the pool.  Problem is, the free memory is fragmented and you are getting the 4031 because a contiguous chunk of memory can't be found in the size you need.

The view v$shared_pool_reserved will show you the size of the object that last failed.

You need to look at "keeping" large and/or frequently used objects (typically procedures) in the shared pool. Having them move in and out causes fragmentation.

You are also on the right track to use bind variables. Received on Wed Aug 29 2001 - 09:20:45 CDT