Sorry having trouble finding it at the moment. Working on a
presentation ... not a big fan of AMM and/or ASMM anyway.

There is some kind of parameter ( maybe underscore parameter ) to have
Oracle back off how often it does the resizing of SGA stuff ... anyone
remember what that is?

Thanks in advance

On Jul 22, 2:00Â*pm, John Hurley <hurleyjo... (AT) yahoo (DOT) com> wrote:
[WARNING: Before changing/adding ANY "underscore" parameter, consult
Oracle Support]
[WARNING: Before changing/adding ANY "underscore" parameter, consult
Oracle Support]
[WARNING: Before changing/adding ANY "underscore" parameter, consult
Oracle Support]

From http://jonathanlewis.wordpress.com/2.../sga-resizing/
Update Sept 2009: If you think that you are suffering problems due to
excess resizing operations, check Metalink for document id 7189722.8 –
which describes this behaviour as a bug “confirmed as affecting
10.2.0.4″. The bug is fixed in 10.2.0.5 and and 11.2, but there is a
workaround offered through a hidden parameter:

alter session set "_memory_broker_stat_interval=999;
The interval is set in seconds, and the default is 30 seconds. I doubt
if there’s any specific significance to the value 999 used in the
demonstration code from the bug note.

On the downside – bug 6528336 was confirmed in 10.2.0.3 and reported
fixed in 10.2.0.4 – so you may still want to be a little cautious
about ASMM even in the latest releases.

[WARNING: Before changing/adding ANY "underscore" parameter, consult
Oracle Support]
[WARNING: Before changing/adding ANY "underscore" parameter, consult
Oracle Support]
[WARNING: Before changing/adding ANY "underscore" parameter, consult
Oracle Support]

"John Hurley" <hurleyjohnb (AT) yahoo (DOT) com> a écrit dans le message de news:
58d62a85-7cdc-4227-9922-7d5244413df7...oglegroups.com...
v$sga_resize_ops

Regards
Michel

On Jul 22, 2:00*pm, John Hurley <hurleyjo... (AT) yahoo (DOT) com> wrote:
A bit of Google digging found a couple that might be what you are
remembering.
You might be thinking of _memory_broker_stat_interval, which I found
briefly described in these two articles:
http://jonathanlewis.wordpress.com/2.../sga-resizing/ (see the
Update note)
http://www.bluegecko.net/oracle/ora-04031-and-asmm/

---
You might also be thinking of the _memory_imm_mode_without_autosga
parameter, described here:
http://www.ora600.be/category/blog/m...withoutautosga

---

John, I know that you are aware of this, but just a warning for anyone
else who might read this message in the future. Changing hidden
parameters should only be performed after consulting with Oracle
support. Just because 2 or 3 articles describe a hidden parameter in
a similar fashion, it is not automatically safe to assume that the
hidden parameter could be safely modified without undesirable side-
effects.

Charles Hooper
Co-author of "Expert Oracle Practices: Oracle Database Administration
from the Oak Table"
http://hoopercharles.wordpress.com/
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

On Jul 22, 4:11*pm, "Michel Cadot" <micadot{at}altern{dot}org> wrote:
v$sga_resize_ops is the view that tells you how frequently it is doing
the resize. I believe the parameter is _memory_broker_stat_interval.

On Fri, 22 Jul 2011 11:00:45 -0700, John Hurley wrote:

You can turn off DB_CACHE_ADVICE.



--
http://mgogala.byethost5.com