ORA-09925: Unable To Create Audit Trail File

APPLIES TO:

Oracle Database - Enterprise Edition - Version 9.2.0.8 and later

Information in this document applies to any platform.

SYMPTOMS

Connections to the database or database startups fail with any of these errors:

ORA-09925: Unable to create audit trail file

Linux-x86_64 Error: 27: File too large

Additional information: 9925

ORA-01075: you are currently logged on

ERROR:

ORA-09925: Unable to create audit trail file

SVR4 Error: 13: Permission denied

Additional information: 9925

ERROR:

ORA-09925: Unable to create audit trail file

Linux-ia64 Error: 28: No space left on device

Additional information: 9925

ORA-01075: you are currently logged on.

CAUSE

1) The free space on the mount point used to dump the audit records is exhausted:

$ df -h

Filesystem Size Used Avail Use% Mounted on

/dev/sda3 448G 448 G 0 100% /

/dev/sda1 190M 26M 155M 15% /boot

tmpfs 3.9G 2.5G 1.4G 65% /dev/shm

2) The mount point is not available or the directory specified by the AUDIT_FILE_DEST parameter does not exist.

3) The number of inodes is exhausted

$ df -i

Filesystem Inodes IUsed IFree IUse% Mounted on

/dev/sda3 121012224 121012224 0 100% /

/dev/sda1 50200 46 50154 1% /boot

tmpfs 1001034 803 1000231 1% /dev/shm

4) The oracle user does not have enough privileges to write to the audit file destination folder

5) Bug 14488943 - ORA-9925 can occur writing audit if ORACLE_PATH is set

SOLUTION

1.Check if directory $ORACLE_BASE/admin/$ORACLE_SID/adump exists. If ORACLE_BASE is not set, then the default audit directory is $ORACLE_HOME/rdbms/audit.

Make sure the permissions on the directory are set to 755.

2.Make sure that there is enough space on the file system to accommodate the newly created audit files.

3.If the inodes are exhausted and cleaning the unwanted files does not help, format the filesystem again with lower bytes per inode to increase the number of inodes for the filesystem. Your system adminsitrator can help you with this task.

4.On 11.2.0.3, this error may be seen when ORACLE_PATH environmentatl variable is set.

As a workaround ORACLE_PATH can be unset.It can be fixed by applying Patch 14488943.

This document has been taken from Oracle Support Doc ID 1993887.1