Friday, December 10, 2010

Something Interesting about the 11g Client

If you're just beginning to implement Oracle 11g, you need to be aware of the Automatic Diagnostic Repository (ADR).  It has nothing to do with AWR, ADDM, ASM, ASSM, or any of the other acronyms Oracle has come up with over the last two releases.

In terms of the database, ADR could be a great thing.  It's integration with Enterprise Manager is probably one of the best parts about the feature.  The database manages the retention policy of how long you want to keep these files around based on the scheduler, all things we know how to deal with.

However, you need to be aware that in a client-only configuration (such as a shared client over NFS) there is nothing to manage the logfiles generated by ADR.  The logs get place in /var/tmp and could potentially be across every machine in your environment.  That could be a nightmare if you're running with several hundred clients or multiple domains.  Left unchecked, it could fill up your root disk if that's where you have /var/tmp. I'll leave it to your imagination how I found out about this new feature.

Instead, you might want to turn ADR off by setting DIAG_ADR_ENABLED=off in your sqlnet.ora file.

1 comment:

Greg said...

ADR is a great addition to the Oracle Database.

ADR has also been adopted as a component along with it's concepts (Problems, Incidents, etc) in Oracle Fusion Middleware. You can find documentation on the FMW integration with ADR here -

Also, check out this blog entry on it -