Re: database monitoring tools - what is your short list of requirements?

Well, as we have over 800 dbs and about 600 servers, I don't reckon
paging is an option... plus we are still only physical DBA (Not apps
dba) so for blocking locks and resource limits we are reactive (when
we get an error or call from customer, we investigate).

Of course, customer doesn't want to pay for a centralized admin tool,
nor does the company... so we are stuck with sql*plus and a couple of
scripts we all share for basic manual monitoring. I've been pressuring
for a while to centralize access to be able to at least automate these
scripts from a single server... this hasn't happene yet.

But Ideally:

* Application related issues
* Error monitoring (namely OERR)
* Resource Consumption
* Capacity Planning
* Backup status and stats
* rogue SQL
* long operations
* security policies
* password centralization (mostly for dba accounts)
* web interface
* and access to diag and tuning packs would be awesome... but the tool
*should* support similar functionality without access to licensed
packs (in order to support SE mainly)j
* a decen interface to wait interface (?)
* overview (really, checking 50 dbs is one thing, checking 800 is
totally different
* support for custom monitoring
* support for monitoring profles (i.e. prod databases need to monitor
this and that, and non-prod database need to monitor these other
things)

I don't know any app that covers all this, however I am slowly working
on an apex/10gXE (it could run on 10g SE, EE and 11g SE, EE,
obviously, but due to licensing costs XE is a good option) based
application that covers all this. (stuck with the wait interface,
obviously). My idea is to release it publicly (still reading through
Oracle's License and GPL/LGPL) and have a free tool for DBAs. (in case
anyone is interested, you can contact me directly and we can set up a
shared development environment, so far it's just a vm on my laptop).

hth
Alan Bort
Oracle Certified Professional



On Wed, Apr 1, 2009 at 6:58 PM, Jared Still <jkstill@xxxxxxxxx> wrote:
> On Wed, Apr 1, 2009 at 2:10 PM, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx>
> wrote:
>>
>> *Blocking locks
>
> That would be a good one to add.
>
>>
>> *Approaching or exceeding resource limits, e.g. sessions, processes,
>> open_cursors
>
> I've only encountered resource limit issues rarely, so I've never monitored
> it myself.
> Still, would be a good idea to do so.
>
>>
>> *Backup failures – I like to get emailed immediately on these, with the
>> option of being paged for critical backups
>
> I get that once a day.  Paging would be nice. Hmm..
>
>
>
--
http://www.freelists.org/webpage/oracle-l


Other related posts: