Other Cricket based work I've done to extend coverage to ATG Dynamo and BEA Weblogic inspired me to tackle Oracle's complex SNMP implementation. Here are the results. Note that you might consider looking at the graphing abilities offered by Oracle Enterprise Manager, which I didn't know existed when I started this project.

I am providing a Defaults file and script for autogenerating target configuration. The script, like other items you would find in $CRICKET_HOME/util, depends on Cricket-provided perl modules.

If you are encountering difficulty enabling Oracle's SNMP support (it is rather complicated), consult the relevant Oracle documentation. OTN should provide access to the documentation for your version. I have successfully used Oracle's master agent to proxy requests to net-snmp in the past, so I'm certain it can be done.

To integrate this work, copy the genOra script to $CRICKET_HOME/util in your cricket installation. Execute it using the options -h to specify the hostname, -p for port and -c for the community name which by default are localhost, 161 and public, respectively. The SID of the database is a mandatory argument. For example, to monitor an Oracle database called "FOO" hosted on foodb with the community name "secretrdbms" you would execute: $CRICKET_HOME/util/genOra -h foodb -c secretrdbms FOO . An appropriate targets file would be emitted on STDOUT. Simply create an oracle subdirectory in your cricket-data tree and place the provided Defaults file in the oracle directory. Create subdirectories, e.g. cricket-data/oracle/FOO, and direct the output of genOra into "targets" files in each subdirectory. Whenever you change the schema or datafiles within the database, you will need to re-run genOra.

(C) 2002, Michael Han
$Id: oracle.html,v 1.6 2003/06/28 22:01:44 mikehan Exp $