Re: Oracle Audit aud$ vs Database Logon Trigger
- From: Sanjay Mishra <smishra_97@xxxxxxxxx>
- To: "saibabu_d@xxxxxxxxx" <saibabu_d@xxxxxxxxx>, free <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 19 Oct 2012 07:43:02 -0700 (PDT)
Thanks Sai for good point.
________________________________
From: Saibabu Devabhaktuni <saibabu_d@xxxxxxxxx>
To: free <oracle-l@xxxxxxxxxxxxx>
Sent: Friday, October 19, 2012 3:31 AM
Subject: Re: Oracle Audit aud$ vs Database Logon Trigger
Sanjay,
Another option would be to scan listener log file for all the connections
coming in to figure out the last login time for each user, assuming listener
log file contents kept long enough.
If you deploy active data guard in future, trigger based auditing will not
work. You can opt for inbuilt auditing based on audit trail.
If the underlying goal is to drop the user's not used the database over the
past X days, then you can also try querying dba_hist_sqlstat awr base table
view by parsing_schema_name to check the last query execution time by user
(this will only work if you are capturing all the sql's in the cache into AWR).
Thanks,
Sai
http://sai-oracle.blogspot.com
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
