comments as always On Mon, 14 Jun 2004 16:06:33 -0600, Daniel Fink <daniel.fink@xxxxxxx> wrote: > > I can't speak for Oracle (nor Sun), but my take is that often these events > are set for a specific purpose, then the reason for > setting them disappears into the mist of time. I love the ones that reference > a TAR that you can no longer view and Support can't > tell you why. Anytime a new version (even a bug fix) is installed, the event > may cause new problems. I agree entirely. > > If there is any other way to deal with a problem, I would definitely do it. And there is.... You can log the errors and associated statements, plus lots of other goodies if you want to a table using a trigger and the system events that are (I think) new in 9. It also has the advantage that you can change what events you monitor, or enable/disable monitoring without bouncing the database. I have an example set of scripts on my site (utility for trapping arbitrary server errors or some such wording) . Naturally since I wrote the script we haven't had a single 1652 (which we were looking for) but you'll get the idea. -- Niall Litchfield Oracle DBA http://www.niall.litchfield.dial.pipex.com P.S. Dan - you might like to check out the creative commons licensing for your intellectual property questions. ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------