Databases
--
Questions
--
Followers
Top Experts
ORACLE ERROR ORA-09817 and ORA-09945
Hi, I am having a problem:
ORA-09817: Write to audit file failed.
Linux Error: 28: No space left on device
ORA-09945: Unable to initialize the audit trail file
Linux Error: 28: No space left on device
It's apparent that the filesystem is full. df shows that there is no space left.
what I would like to know is how to move the tablespace to another filesystem temporarily to clean up the filesystem
because I couldn't connect / as sysdba anymore
Thanks
ORA-09817: Write to audit file failed.
Linux Error: 28: No space left on device
ORA-09945: Unable to initialize the audit trail file
Linux Error: 28: No space left on device
It's apparent that the filesystem is full. df shows that there is no space left.
what I would like to know is how to move the tablespace to another filesystem temporarily to clean up the filesystem
because I couldn't connect / as sysdba anymore
Thanks
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Which Oracle version are you using?
In 9i,try connecting as sys:
sqlplus /nolog
connect sys/change_on_install@<sid
where change_on_install is the default password..
In 9i,try connecting as sys:
sqlplus /nolog
connect sys/change_on_install@<sid
where change_on_install is the default password..
markchih, you have to move other files that are not Oracle files to a new location to release the space to solve the problem. Or you can delete/move the old archived log files if possible.
For your information Oracle always generate an audit (.aud) file when you connect INTERNAL, regardless of whether auditing has been turned on in the database and this is a security feature and expected behavior. So if the systemfile is full you will get trouble when trying to connect
Hope this helps
For your information Oracle always generate an audit (.aud) file when you connect INTERNAL, regardless of whether auditing has been turned on in the database and this is a security feature and expected behavior. So if the systemfile is full you will get trouble when trying to connect
Hope this helps
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Your audit file destination is full.
"show parameter aud" will tell you where audit_file_dest is.
Using your operating sysdtem commands, delete most (or all) of your.aud files.
Or you can compress them into a zip or tar file.
Alternately add space if you don't want to do either of the above.
The first message (from catchmeifuwant) gives you instructions that should let you login to the database if your problem had been a full archive log destination. Try logging in as a non-sysdba user as that won't require a .aud file.
HTH
"show parameter aud" will tell you where audit_file_dest is.
Using your operating sysdtem commands, delete most (or all) of your.aud files.
Or you can compress them into a zip or tar file.
Alternately add space if you don't want to do either of the above.
The first message (from catchmeifuwant) gives you instructions that should let you login to the database if your problem had been a full archive log destination. Try logging in as a non-sysdba user as that won't require a .aud file.
HTH
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Databases
--
Questions
--
Followers
Top Experts
Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.