Re: DDL auditing - *Extremely* detailed

From: Richard Foote <richard.foote_at_bigpond.com>
Date: Tue, 4 May 2004 23:16:13 +1000
Message-ID: <147b01c431d9$f9965620$0100000a@FOOTE>

One issue I've come across with using logminer to determine who's done what, is if changes are made via stored programs (procedures, triggers and the such) which is not uncommon, then the USERNAME column is populated with the owner of the stored program, not the actual user who's done the dirty work.

Can be a trap for the unwary.

Cheers

Richard
----- Original Message -----

From: "Tanel Põder" <tanel.poder.003_at_mail.ee> To: <oracle-l_at_freelists.org>
Sent: Tuesday, May 04, 2004 10:00 PM
Subject: Re: DDL auditing - *Extremely* detailed

One alternative way would be to use logminer if your transaction_auditing parameter is set true (default in 9.2), that way you'll get quite a lot of information about the user into the redolog as well, when they start the DDL recursive transaction...

Tanel.

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.
--

Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html

Received on Tue May 04 2004 - 08:11:14 CDT