Re: Oracle Audit aud$ vs Database Logon Trigger
- From: Sanjay Mishra <smishra_97@xxxxxxxxx>
- To: "Lange, Kevin G" <kevin.lange@xxxxxxxxxx>, Michael Dinh <mdinh235@xxxxxxxxx>
- Date: Thu, 18 Oct 2012 14:32:44 -0700 (PDT)
Thanks Kevin. One good point is that we can exclude some user with logon code
which might be one of the requirements for some of the default Database Schema
as well as some Application schema. Agree with Mike and your point that Audit
is integrated and might even purge based on requirement using Oracle commands.
Thanks for the time as i am trying to collect the points to finalize the
approach
Rgds
Sanjay
________________________________
From: "Lange, Kevin G" <kevin.lange@xxxxxxxxxx>
To: smishra_97@xxxxxxxxx; Michael Dinh <mdinh235@xxxxxxxxx>
Cc: oracle-l <oracle-l@xxxxxxxxxxxxx>
Sent: Thursday, October 18, 2012 10:57 AM
Subject: RE: Oracle Audit aud$ vs Database Logon Trigger
I use both for different databases and reasons. I think I like the logon
trigger more simply because it is more customizable on what data is recorded.
Plus, it's a lot easier to exclude certain IDs in the logon trigger than it is
in the Oracle Auditing. Of course, auditing is written by Oracle and
integrated into the system (as opposed to one of us writing a logon trigger) so
I tend to think that the code is beter and less of a drag on the system.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Sanjay Mishra
Sent: Thursday, October 18, 2012 9:40 AM
To: Michael Dinh
Cc: oracle-l
Subject: Re: Oracle Audit aud$ vs Database Logon Trigger
Thanks Mike. Do we have any pros and cons for both approach. This database is
heavily accessed in terms of logon like 500+ user anytime and has 3000+ user in
the database. So want to explore as use this approach for this many user or so
based on maintenance and reliability.
Tx
Sanjay
________________________________
From: Michael Dinh <mdinh235@xxxxxxxxx>
To: smishra_97@xxxxxxxxx
Cc: oracle-l <oracle-l@xxxxxxxxxxxxx>
Sent: Wednesday, October 17, 2012 11:28 PM
Subject: Re: Oracle Audit aud$ vs Database Logon Trigger
I would use audit functionality for simplicity.
AUDIT SESSION WHENEVER SUCCESSFUL;
Query DBA_AUDIT_SESSION
Use DBMS_AUDIT_MGMT to manage.
HTH
-Michael.
On Wed, Oct 17, 2012 at 7:32 PM, Sanjay Mishra <smishra_97@xxxxxxxxx> wrote:
Hi
>
>Can someone help as what is best approach in term system performance and best
>practices for auditing. Requirements is only to check what user has not logon
>to the database in x number of days and create a report on daily basis.
>Requirement is to report user who has not logon to the database in last 180
>days. So what is best practices like to use Audit command or Database Logon
>Trigger. Any help in providing any fact is highly appreciable
>
>TIA
>Sanjay
>
>
>--
>//www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
