Re: Oracle Audit aud$ vs Database Logon Trigger

From: Sanjay Mishra <smishra_97_at_yahoo.com>
Date: Thu, 18 Oct 2012 07:39:41 -0700 (PDT)
Message-ID: <1350571181.13242.YahooMailNeo_at_web122101.mail.ne1.yahoo.com>

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_at_gmail.com> To: smishra_97_at_yahoo.com
Cc: oracle-l <oracle-l_at_freelists.org> 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_at_yahoo.com> 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
>
>
>--
>http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Thu Oct 18 2012 - 16:39:41 CEST