Re: Endless auditing files !! V7.0.16.4

> A. Pandya writes:

> Oracle v7.0.16.4 release and probably later versions
> incur auditing files being created in $ORACLE_HOME/rdbms/audit. There is
 

> an init.ora parameter (undocumented) available which will stop the files
 

> from being created and flooding up disk space. Please advise on any
> whereabouts of this behaviour.

I am not aware of any undocumented parameters, but can offer the following documented parameters to affect the behavior of auditing. These may be in your init.ora or config.ora files, else you will get the operating system defaults (in which case you will want to over-ride the ones you do not like):

audit_trail- (values NONE, DB or OS). Determines whether the audit trail is written to database tables (DB), operating system files (OS) or is not written at all (NONE).

To determine what (and therefore how much) gets audited, you would issue the SQL audit command. For information as to what can be audited and its implications, see chapter 13 of the Oracle 7 Server Administrator's Guide.

If you do not want any auditing, you can simply set the audit_trail initialization parameter to none. If you want some, you can put it in either the tables or the files and routinely purge these files (you can even develop scripts to perform automatic purges). I would think that if you only want to keep say a week's worth of data it may be easier to put it in the database table (sys.aud$) file where you can issue the SQL delete command with a where clause specifying that you only want old data purged.

Hope this helps. Received on Sat Mar 04 1995 - 02:00:11 CET