RE: Question Auditing Session = Logons (inspired by Stephen's email)

From: Herring Dave - dherri <>
Date: Thu, 28 Feb 2013 16:33:36 +0000
Message-ID: <>

Even if on 11.2, validate how monitoring software (if it exists) connects. I found a number of situations where EM was configured by default to connect as SYSDBA.

Acxiom Corporation

TEL    630.944.4762
MBL   630.430.5988 

1501 Opus Pl, Downers Grove, IL 60515, USA WWW.ACXIOM.COM -----Original Message-----
From: [] On Behalf Of Tanel Poder Sent: Wednesday, February 27, 2013 5:01 PM To:
Cc: Oracle-L Freelists
Subject: Re: Question Auditing Session = Logons (inspired by Stephen's email)

Are you auditing into the OS files then? (not to AUD$?) Logins via SYSDBA/SYSOPER will always generate an .aud file, no way around it.

And in 11.1 there's a bug 9744092: EXCESSIVE AMOUNT OF AUD FILES BEING GENERATED IN 11.1 - which causes even regular (non-sysdba) application logins create audit files.

*Tanel Poder*
Enkitec (The Exadata Experts)
Training <> | Troubleshooting<>
 | Exadata<>
 | Voicee App <>

On Wed, Feb 27, 2013 at 9:14 PM, <> wrote:

> Can you audit the other things without auditing SESSION (Logons) ?
> We have a scenario where we're generating thousands of .aud files per day
> - and our user population is not very large.
> I've just started investigating this and want to reduce the number of aud
> files generated.
> We have some applications that all they do is connect to the database and
> disconnect to verify it is up. And they do this several times a minute
> from different servers; an issue which is on "the list" to be addressed.
> Chris Taylor
> Oracle DBA
> Parallon IT&S
> --
-- *************************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. **************************************************************************** --
Received on Thu Feb 28 2013 - 17:33:36 CET

Original text of this message