I received this error message when I started my virtual machine and tried to logon to my database as sysdba to startup the instance.
[oracle@node1 ~]$ sqlplus / as sysdba
ERROR:
ORA-09925: Unable to create audit trail file
Linux Error: 30: Read-only file system
Additional information: 9925
ORA-09925: Unable to create audit trail file
Linux Error: 30: Read-only file system
Additional information: 9925
- I rebooted my machine and got following messages which pointed to some errors encountered during filesystem check and instructed to run fsck manually.
[root@node1 ~]# init 6
Checking filesystems
/: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
*** An error occurred during the filesystem check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
– I entered password for root to initiate filesystem check. As a result I was prompted multiple no. of times to allow fixing of various filesystem errors.
(Repair filesystem) 1 # fsck Fix(y)?
- After all the errors had been fixed, filesystem check was restarted
Restarting e2fsck from the beginning... /: ***** FILE SYSTEM WAS MODIFIED ***** /: ***** REBOOT LINUX *****
- After filesystem had been finally checked to be correct, I exited for reboot to continue.
(Repair filesystem) 2 # exit
– After the reboot, I could successfully connect to my database as sysdba .
[oracle@node1 ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Sat Jul 12 09:21:52 2014
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL>
I hope this post was useful.
Your comments and suggestions are always welcome.
—————————————————————————————–
Related Links:
————-
Nice Posts , I would suggest ,when you get this error always verify the mount point space availability as the first thing ,that may also prompt the same error and we should be able to fix these issues online .
You are correct but in this case I had resort to fsck as the whole filesystem had been mounted Read only.
Thanks for your feedback.
Regards
Anju Garg
Were you able to figure out why the mount became read only?I have seen a similar case but no root cause is yet identified.
Good piece of information:)
Also we need to look at the inode usage, we faced similar issue where sufficient space was available at the mount point but inode was 100% full and preventing from creating new audit files. Thanks Anju Garg for creating a fantastic repository.
Hi Lokesh,
Thanks for this information.
Your comments andd suggestions are always welcome!
Regards
Anju Garg