Re: AUDIT_FILE_DEST

In article <882562455.949420043_at_dejanews.com>,

        mmorga2_at_amfam.com writes:
> Greetings,
>
> We are running Oracle 7.3.2.3 on an IBM RS/6000 - AIX 4.1.5
>
> As you may know, Oracle writes an audit file (ora_<pid>.aud) to the
> AUDIT_FILE_DEST whenever anyone does a CONNECT INTERNAL. This cannot be
> disabled. Oracle calls this a "security feature". Well, in our
> environment today, security is not a high priority (tomorrow that may
> change). However, free diskspace IS a concern.
>
> Here's my question ....
>
> In order to keep Oracle's security feature from filling up my filesystem
> (and save me the work of periodically deleting hundreds of .aud files),
> what are the ramifications of assigning /dev/null to AUDIT_FILE_DEST? I
> realize that, if I wanted to view an audit file, I would not be able to.
> But as I said, being able to audit whenever someone connects internal is
> not important today.
>
> Thanks,
> Mike Morgan

Mike,

        Why not try it? I did.

oracle_at_sequeira:~$ svrmgrl

Oracle Server Manager Release 2.3.2.0.0 - Production

Copyright (c) Oracle Corporation 1994, 1995. All rights reserved.

Oracle7 Server Release 7.3.2.2.0 - Production Release With the distributed option
PL/SQL Release 2.3.2.2.0 - Production

SVRMGR> connect internal
Password:
ORA-09925: Unable to create audit trail file AT&T System V/386 Error: 20: Not a directory Additional information: 9925
SVRMGR>         Regards.

Tony

-- 
S. A. Sequeira tony_at_sequeira.powernet.co.uk