Non critical error ORA-48180 caught while writing to trace file

Non critical error ORA-48180 caught while writing to trace file

Database Version: 11.2.0.4 with ASM

Operating System: Red Hat Enterprise Linux Server release 6.4 (Santiago)

Error Description:

In Alert.log file:

Tue Dec 16 12:10:06 2014

Non critical error ORA-48180 caught while writing to trace file "/u01/app/oracle/diag/rdbms/rpst01/rpst01/trace/rpst01_ora_30396.trc"

Error message: Linux-x86_64 Error: 28: No space left on device

Additional information: 1

Writing to the above trace file is disabled for now on...

OS Audit file could not be created; failing after 6 retries

Tue Dec 16 12:10:06 2014

Non critical error ORA-48180 caught while writing to trace file "/u01/app/oracle/diag/rdbms/rpst01/rpst01/trace/rpst01_ora_30401.trc"

Error message: Linux-x86_64 Error: 28: No space left on device

Additional information: 1

Writing to the above trace file is disabled for now on...

OS Audit file could not be created; failing after 6 retries

OS Audit file could not be created; failing after 6 retries

OS Audit file could not be created; failing after 6 retries

There are many blogs which suggests to increase MAX_DUMP_FILE_SIZE but this is not the case.

In my case I checked the size and found it already set to UNLIMITED.

SQL> show parameter MAX_DUMP_FILE_SIZE

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

max_dump_file_size                   string      unlimited

I was also getting below error while trying to login into the database with OS authentication.

[oradb@litm##### dbs]$ export ORACLE_SID=rpst01

[oradb@litm##### dbs]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Tue Dec 16 12:13:40 2014

Copyright (c) 1982, 2013, Oracle.  All rights reserved.

ERROR:

ORA-09925: Unable to create audit trail file

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

Additional information: 9925

ORA-01075: you are currently logged on

Solution:

1.       Go to audit_file_dest directory.

2.       Remove *.aud files.

3.       If files are too many then you may get below error

[oradb@litm##### adump]$ rm -rf *

-bash: /bin/rm: Argument list too long

4.       To overcome error, execute below command

find . -name "*.aud" -print | xargs rm

5.       Try to login into your database, it should be successful.

6.       Error should also disappear from alert.log file.