Re: Oracle's Audit Feature: What? How?

From: Marek Wiechula and Sheila Plant <sparemgw_at_batelco.com.bh>
Date: 1996/09/14
Message-ID: <323B341F.4D11_at_batelco.com.bh>#1/1


Barry Johnson wrote:
>
> Of those who use Oracle's Audit capability, care to share any
> advice on what you audit (system, statement, object) and how
> (session v. access)? I seek it in the context of larger-scale,
> mission-critical systems...
>
> I'd also appreciate insights into its resource requirements:
> processing overheads, storage demands, whatever...
>
> TIA...BJ
> --
> Barry Johnson - BJohnson_at_WorldBank.Org

Most of our applications developers find the audit feature inadequate for the things they want to track and rely on triggers for the detailed information.

I use AUDIT SESSION from a DBA standpoint to monitor who is on when. I find this helpful especially when some users are rather vague about exactly when they ran into a particular problem. Storage requirements are not too unreasonable but they will get out of hand if you don't adopt some kind of policy about how much audit history you want to keep.

I am considering adding auditing on creating and dropping various objects.

Marek Wiechula Received on Sat Sep 14 1996 - 00:00:00 CEST

Original text of this message