If you have increased the size it is likely bacause of fragmentation. Pin pl/sql on database startup. and pin sql soon after startup. Get dev to use bind variables.
You could change the cursor_sharing parameter too but that is avoidable.
Avoid ad hoc sql queries to database.
"Smith, Ron L." <rlsmith@(protected):
I have a couple of unrelated Oracle 8.1.7 databases that occasionally
getting the following error:ORA-04031
: unable to allocate 4200 bytes of shared memory ("shared
pool","unknown object","sga heap","state objects")=20
Flushing the Shared Pool does not help the problem. The size of the
Shared Pool has been increased several times, but doesn't appear to
help. Neither database is very busy.
One of the databases serves as a "Gateway" database between a 7.3.4 and
a 9.2 database just for connectivity. The other is just a straight
8.1.7 OLTP database.
Bouncing the database ALWAYS corrects the problem for several weeks.
Can anyone help be diagnose the problem?
If you are not the intended recipient of this e-mail message, any use, =
distribution or copying of the message is prohibited.
Please let me know immediately by return e-mail if you have received =
this message by mistake, then delete the e-mail message.
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web