What information to gather

From: Guillermo Alan Bort <cicciuxdba_at_gmail.com>
Date: Wed, 1 Jul 2009 14:12:41 -0300
Message-ID: <172762180907011012w141ecab3y25d602faf0efdb17_at_mail.gmail.com>

I know this *might* be a bit of a repeated thread. However... here I go.

Due to reasons to boring to get into, the company I work for is not going to invest in a monitoring tool. However, we have a few DBs that work only as RMAN catalogs. Servers are oversized so we can build new DBs there. I wanted to have a central repository of information for our databases... so I was wondering what information to take.

What I have so far:

DB Name
Parameters (v$parameters)
archive deestination
backup status (last backup and all backup drilldown). Performance information (I'm still working on this, either statspack or awr reports/snapshots)
Space management (tablespaces, datafiles, autoextend, extent management, segment space management, size, free space, etc) User management (users, account status, etc)

There will be no real time information, so hang analysis and such will not be possible, plus information from v$ views won't be that useful.

The idea with this is that the data will be updated in the central DB and it will be accessed via a APEX application I'm developing (thank god for APEX... I am a fairly good PL/SQL developer but simply refuse to write java, so APEX gives a good alternative, if a bit slow)

thanks in advance.
Alan Bort
Oracle Certified Professional

Received on Wed Jul 01 2009 - 12:12:41 CDT

Original text of this message