RE: RE: DBA Support Database

I have seen something of the kind done at one of my large customers (600+ databases, Oracle + Sybase), where I have had more than a hand into the Oracle part (the inventory is stored in *blush* Sybase) and I am working on something similar with a colleague elsewhere, where there are _only_ 80 databases. In both cases the idea is to store an inventory, and to have scripts (tcl at one place, ksh at the other) running once a day to update the inventory; it of course requires having a suitable account with the required privileges created on each database. Inventory set up has been done at one place by scanning possible listener ports over the network, sending lsnrctl stat everywhere. Of course some cleanup required afterwards (... to remove extproc, among other things ...). Information collected involves startup time, Oracle version, tablespace information (also stored to an history table), database links - whatever you wish. For applications, it's a bit more manual. It's easy to get how much space is used by each schema (except SYS, SYSTEM, OUTLN ...) but then you have to 'attach' a schema to an application - and of course a DBA to an application as well. If some standards are respected, it's not too difficult ... The interface has been written with PHP at both places, with regular generation of colorful PDF reports for the management. Looks a bit like reinventing OEM, but the big advantage is that you can plug whatever you want into the system. At the biggest customer, it's linked to a similar system set up by the sysadmins showing all the information you can dream of about servers, hardware-wise as well as software-wise. Pretty impressive.

For the record, the (huge team) of DBA there has at one point been forced upon some 3rd party software but they are much happier with their tools.

HTH SF

>----- ------- Original Message ------- -----
>From: "Vergara, Michael (TEM)"
><mvergara_at_guidant.com>
>To: Multiple recipients of list ORACLE-L
><ORACLE-L_at_fatcity.com>
>Sent: Thu, 30 Oct 2003 08:29:27
>
>We recently signed a corporate agreement with
>Oracle that basically
>gave us a named-user license for every person in
>the company. Now,
>we have databases sprouting like rabbits. Our
>four-dba team now
>is supporting SAP, two different Siebels, a data
>warehouse, and
>myriad other projects - over 200 databases so far.
>
>I have recently been tasked with a similar project,
>so I am
>also very interested in knowing if this has been
>done before.
>In-house, purchased, anything?
>
>Thanks,
>Mike
>
>
>-----Original Message-----
>Sent: Thursday, October 30, 2003 8:09 AM
>To: Multiple recipients of list ORACLE-L
>
>
>Ron:
>
>I have heard of this being done especially in large
>companies that have
>many, many databases. It is difficult to keep
>track of all the little
>details that are spread out all over the company.
>Having a central data
>mart for this information I thing would be very
>helpful. The only problem I
>see is keeping it up to date.
>
>Ken Janusz, CPIM
>
>
>----- Original Message -----
>To: "Multiple recipients of list ORACLE-L"
><ORACLE-L_at_fatcity.com>
>Sent: Thursday, October 30, 2003 9:29 AM
>
>
>> I was thinking about putting together a database
>that contains a list of
>> DBAs, servers, databases, and applications. The
>database would be used
>> by the Helpdesk and Management to see who is
>responsible for a given
>> application or database when problems occur.
>>
>> I thought I would check first and see if anyone
>has already designed
>> such a database and might be willing to share it.
>
>>
>> Thanks!
>> Ron Smith
>> --

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Stephane Faroult
  INET: sfaroult_at_oriolecorp.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).