Re: audit_trail=db Overhead ?

Setting AUDIT_TRAIL=DB just allows you to enable audit. It, by itself, has no load.

I have AUDIT_TRAIL=DB and AUDIT SESSION with about 100 connections a minute and haven't noticed any performance impact. But, then, I haven't set an STATEMENT or OBJECT audit options. I have a daily SQL job which queries the audit view to identify failed login attempts
and another job to purge the audit trail of data more than 7 days old. Hemant

At 03:28 AM 21-03-03 -0800, you wrote:

>What would be the overhead of setting audit_trail=db in init.ora
>on the overall database performance ?
>
>NOTE - This is a heavily loaded Hybrid Database having 4000 concurrent users
>
>What optional settings may be better ?
>
>Thanks
>
>--
>Please see the official ORACLE-L FAQ: http://www.orafaq.net
>--
>Author: VIVEK_SHARMA
> INET: VIVEK_SHARMA_at_infosys.com
>
>Fat City Network Services -- 858-538-5051 http://www.fatcity.com
>San Diego, California -- Mailing list and web hosting services
>---------------------------------------------------------------------
>To REMOVE yourself from this mailing list, send an E-Mail message
>to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
>the message BODY, include a line containing: UNSUB ORACLE-L
>(or the name of mailing list you want to be removed from). You may
>also send the HELP command for other information (like subscribing).

Hemant K Chitale
My personal web site is : http://hkchital.tripod.com Received on Fri Mar 21 2003 - 08:31:58 CST