|
|
|
|
|
Re: shared pool [message #460801 is a reply to message #460800] |
Mon, 14 June 2010 20:55 |
|
BlackSwan
Messages: 26766 Registered: January 2009 Location: SoCal
|
Senior Member |
|
|
You are attacking the symptom; not the root cause.
Tell us about the application that is abusing Oracle.
post a copy of your current pfile
>the shared pool utilisation spikes up again to 5 gig and we run into ora 04031 when sga reaches its peak
I have no idea why such demands are placed upon the SGA.
One approach I used in the past to avoid ORA-04031 was to PIN all PL/SQL packages in the application into SGA via DB STARTUP trigger.
They consumed only about 1.5GB & never saw this error again.
[Updated on: Mon, 14 June 2010 22:36] Report message to a moderator
|
|
|
Re: shared pool [message #460955 is a reply to message #460801] |
Tue, 15 June 2010 13:23 |
mikerault
Messages: 21 Registered: June 2010 Location: Alpharetta, Ga
|
Junior Member |
|
|
Are you using AMM (sga_target, sga_max_size)? You may want to disable AMM and just use base parameters for sizing your components. Also, run an AWR or Statspack and see what is happening as far as SQL versions. Are you using CURSOR_SHARING? A setting of SIMILAR can result in multiple SQL versions, even when not needed. Set it to FORCE or set the undocumented parameter _sqlexec_progression_cost to its maximum value.
Mike
|
|
|
|
|
|