Re: MMON slaves spinning
- From: De DBA <dedba@xxxxxxxxxx>
- To: Mark Burgess <mark@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 02 Dec 2013 09:37:15 +1000
Hi Mark,
This is also strange. The production database undergoes much less resizing than
the staging:
Operation count:
Prod Stg2
------------- ----- -------
Shared Pool 5 11
Large Pool 77 575
Java Pool 0 0
Stream Pool 0 0
Buffer Cache 82 586
Size (GB)
Prod Stg2
------------- ---------- ----------
Shared Pool 1.375 0.938
Large Pool 0.125 0.063
Java Pool 0.063 0.016
Stream Pool 0.063 0
Buffer Cache 0.875 1.546
Cheers,
Tony
On 29/11/13 14:07, Mark Burgess wrote:
Hi Tony,
what do the memory resize ops stats look like?
Regards,
Mark
On 29 Nov 2013, at 2:15 pm, De DBA <dedba@xxxxxxxxxx <mailto:dedba@xxxxxxxxxx>>
wrote:
Possible, but the production database sees way more inserts/updates and there
it is not a problem. You'd think the gather stats job has more to do in
production... Also, I think that the gather stats job runs inside the
management window, and the spinning starts just after that is closed..
On 29/11/13 13:01, Rich wrote:
<..snip..>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
