Re: v$rowcache outstanding_alerts

From: Tanel Poder <tanel_at_tanelpoder.com>
Date: Thu, 15 Nov 2012 03:16:58 +0200
Message-ID: <CAMHX9JJfgnKqtwx-Cqs6W01NNoXRcAFfuo9WQF2yRwvOKAC_CA_at_mail.gmail.com>

It's used for server alerting infrastructure (metrics thresholds, tablespace space etc)
DESC dba_outstanding_alerts
DESC dbms_server_alert
SELECT * FROM v$alert_types;

I wouldn't worry about the miss ratio as this may be just due to the alerts being read infrequently (after they've been aged out from cache) and this number has accumulated over a long time...

-- 
*Tanel Poder*
Blog - http://blog.tanelpoder.com
App  - http://voic.ee


On Thu, Nov 15, 2012 at 12:46 AM, Walker, Jed S <
Jed_Walker_at_cable.comcast.com> wrote:



> I am looking in the v$rowcache table and found something that I haven't

> been able to find out about.

> PARAMETER                             COUNT MODIFICATIONS       GETS

>  GETMISSES   MISS_PCT

> -------------------------------- ---------- ------------- ----------

> ---------- ----------

> ...

> outstanding_alerts                        4           739      59443

>  56431      94.93

>

> Does anyone know what this particular item is, and why it would have such

> a high miss percentage?

>

> Thanks,

>

> Jed

>

>

> --

> http://www.freelists.org/webpage/oracle-l

>

>

>



--
http://www.freelists.org/webpage/oracle-l

Received on Thu Nov 15 2012 - 02:16:58 CET