Old Problem. Flushing the Shared Pool may not defrag memory, according to one Oracle paper I've seen. There definitely is a bug, memory leak, or whatever you want to call it, with early versions of Oracle 7. We had to pin a package in memory in order for it to execute without the dreaded 4031. Flushing the pool seemed to be the only way to pin the package during working hrs should it become unpinned (various things caused that to happen, certainly stopping and resarting the instance did). If you have certain things that have to execute regularly, put them in a stored procedure (package), and have your dba pin it in memory. Some help I hope. Larry Received on Tue Oct 15 1996 - 00:00:00 CEST
Original text of this message