Manage Audit File Directory Growth with cron
(Doc ID 1298957.1)
Last updated on MARCH 15, 2021
Applies to:Oracle Database Products > Exadata > Database Machine
Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 29-Apr-2013***
The audit file destination directories for an ASM instance can grow to contain a very large number of files if they are not regularly maintained. Having a very large number of files can cause the file system to run out of free disk space or inodes, or can cause Oracle to run very slowly due to file system directory scaling limits, which can have the appearance that the ASM instance is hanging on startup.
This document explains how to use the Linux cron(8) utility to manage the number of files in the audit file destination directories.
These steps must be performed for the ASM instance on every database server.
This document explains how to manage the audit file destination directories for ASM instances only. For complete database auditing overview and instruction on managing and purging the database audit trail, refer to the Oracle Database Security Guide at http://download.oracle.com/docs/cd/E11882_01/network.112/e16543/auditing.htm#BCGIDBFI .
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!