Regarding alert log monitor...I have been using a highly adapted version of
Connor McDonald's, uses the dd command to clip off new sections of the alert
log.  Here are a few of the features of my script.

   * Will run from a single copy in a single NFS mounted directory.
   * Can process oratab and hit all databases on host, only need a single
cron entry for all database.
   * Command line switches can roll/trim the alert log and keep it at a
constant size.
   * You can operate in paranoid mode which sends you email for all
unrecognized patterns.
   * You can set it to page for db up/down events.
   * It will monitor for physical structure changes and automatically call
control file backup script.
   * You can set options for email delivery and paging. 
   * You can force the immediate trim/roll and email delivery of any log.
   * Easy to modify to segment known non-critical errors from stuff I want
to get paged about.

Regarding RRD tool...I integrated my performance charting software with MRTG
(www.mrtg.org) some time back.  It is a lot easier to use than RRD.
Currently I just use an access database to see my charts and print them to
nice pretty reports.  I perform the same type of aggregation series at RRD
and MRTG so I can easily keep a year's worth of performance metrics in a
small amount of space.  I will be re-integrating with MRTG so the client can
see the charts a bit easier in a bit.

Regarding the general concept of developing new tools...good luck...the idea
is good, why don't we take the best ideas and apply them to one or two good
solutions that will work for everyone. My experience is that the guy with
the idea will end up doing 99.9% of the work and fizzle out at 80% of the
project.  Would be best to start really small and focused and see what
happens.

Jared...Thanks for the DBI message board links, my friend found the solution
to his trouble there.

- Ethan Post
  


-----Original Message-----
Sent: Tuesday, January 08, 2002 9:46 AM
To: Multiple recipients of list ORACLE-L


...DBA tools written in Python? Hey that was my idea! :-)  

Python is great!!! We have a ton of operational Python scripts to support
application administration and all the data is stored in Oracle. I've
piggy-backed on the development efforts of other Python newbies and the code
is quite readable... in stark contrast to newbie Perl code!

I've developed DBA tools and monitoring stuff in PHP and Perl but now I'm
entertaining a redo and consolidation into Python with RRDTool graphing.
(I'm still anxiously awaiting Jared's book with TONS of Perl!! :-) Regarding
drivers, do you use cxOracle or DCOracle? Database access with Perl is more
mature. I like PHP because it's SO GOOD (and easy) for generating web pages
but I haven't found Python/HTML integration to be as good. Have you used the
Zope stuff? I'm thinking Zope will help for HTML/XML integration but it
seems like overhead and too much of a learning curve. Nevertheless, the
object orientation of Python/Zope should help once you learn it.

Any plans to publish and collaborate development in a forum like
SourceForge? I'm thinking the collaborative development efforts of folks in
the DBA community could produce something better than current commercial
offerings (especially Oracle's OEM) and the resulting tool set would be
extensible, customizable and FREE. Is anyone interested in this? 


DBA's are Duhvelopers too!

Steve Orr,
Bozeman, Montana

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Post, Ethan
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (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).

Reply via email to