Re: Shared memory problem on Oracle 7.2.3

Andre Vergison (avergison_at_infosoft.be) wrote:
: Oracle Server 7.2 Messages manual says :
 

: quote
 

: ORA-04031 unable to allocate num bytes of shared memory num, num,
: num
 

: Cause: More shared memory is needed than was allocated in the operating
: system process. SGA private memory has been exhausted
 

: Action: Either use the DBMS_SHARED_POOL package to pin large
: packages, reduce your use of shared memory, or increase the amount of
: available shared memory by increasing the value set for the
: SHARED_POOL_SIZE initialization parameter.
 

: unquote
 

: I just got a reply from Sridhar Subramaniam <avion_at_ozemail.com.au>
: concerning pinning packages. ("Keeping stored procedures in the shared
: pool ?" in this newsgroup)
: Sridhar mentions the ora-4031 as well.

This would be fine, and it can be a work-around if (and only if) a site is properly set up with the various processes using shared procedures. However, the cookbook answer doesn't address in any way the very simple fact that Oracle 7.2 has a severe memory leak problem (actually, a garbage collector problem ... the garbage collector seems to mainly be garbage).

--
Names:	Bill Beaton			beatonb_at_cadvision.com
					Bill_Beaton_at_digitech.ab.ca
Phone:	(403) 295-3254 (Home)		(403) 266-8622 (work)