RE: Measure database availability beyond 99.9%
Date: Fri, 29 Aug 2008 15:05:53 -0400
We have had the same experience with EM Grid Control.
Unfortunately we have not yet had the time to investigate other tools, but how about this: Build a heartbeat table and schedule a database job (i.e. dbms_scheduler) to insert into that table every x seconds. (the value of x depends on the needed precision).
Then you can build your own reports/alerts based on the data in that table. We use this approach for checking the streams availability as recommended in Note:418755.1 - 10.2.0.x.x Streams Recommendations
Vlado Barun, M.Sc.
Senior Database Architect
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Ingrid Voigt Sent: Thursday, August 28, 2008 3:10 PM
Subject: Measure database availability beyond 99.9%
we are looking for a tool to measure and report the availability of our databases in the HA range, i.e. with high precision. At this time we are only interested in the database state, not whether the customers can work.
The database versions involved are 9.2 - 10.2, 11 coming next year. All editions: SE1, SE and EE.
So far, we have been using EM Grid Control, but beyond 99,9% this is not precise enough. Too many failures of the agent/the Grid Control system rather than the database and too much time between "database back up" and "agent notices that database is back up". A switch in the failsafe clusters takes less than a minute and should be reported to the second, if possible.
We can get startup time easily from a database trigger or the alertlog, but have not good way to measure shutdown time so far. Is there something good available (free would be nice) or do we have to build it ourselves?
Thanks for your help.
http://www.freelists.org/webpage/oracle-l Received on Fri Aug 29 2008 - 14:05:53 CDT