Manage ASM Audit Files with syslog
Last updated on JANUARY 30, 2017
Applies to:Linux OS - Version Oracle Linux 5.9 and later
Oracle Exadata Storage Server Software - Version 126.96.36.199.0 and later
Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Information in this document applies to any platform.
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 syslog facility to manage ASM auditing records so that ASM auditing records are recorded by the operating system syslog facility instead of individual files in the audit_dump_dest directory.
These steps must be performed for the ASM instance on every database server.
This document explains how to manage the auditing records 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 .
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms