Re: database monitoring tools - what is your short list of requirements?
Date: Thu, 2 Apr 2009 08:21:46 +0100
I missed it, likely because of the other thread. Storage, tablespace usage and filesystem usage. App server - availability, filesystem usage. Application - availability, failed jobs, failed logins. Standby databases - log shipping progress, log application progress. So pretty much things that you don't want to discover at a critical moment. I also tend to think from the app down not the db up.
On 4/1/09, Allen, Brandon <Brandon.Allen_at_oneneck.com> wrote:
> Only a few more things I can think of:
> *Blocking locks
> *Approaching or exceeding resource limits, e.g. sessions, processes,
> *Backup failures - I like to get emailed immediately on these, with the
> option of being paged for critical backups
> From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
> On Behalf Of Jared Still
> What would you say are the essentials for database monitoring?
> Privileged/Confidential Information may be contained in this message or
> attachments hereto. Please advise immediately if you or your employer do not
> consent to Internet email for messages of this kind. Opinions, conclusions
> and other information in this message that do not relate to the official
> business of this company shall be understood as neither given nor endorsed
> by it.
-- Sent from Google Mail for mobile | mobile.google.com Niall Litchfield Oracle DBA http://www.orawin.info -- http://www.freelists.org/webpage/oracle-lReceived on Thu Apr 02 2009 - 02:21:46 CDT