Oracle Database Discussions

Error:-
abae:DB:ORAPROD >sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Jul 10 09:47:43 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
ERROR:
ORA-09817: Write to audit file failed.
IBM AIX RISC System/6000 Error: 89: Invalid file system control data detected
ORA-01075: you are currently logged on

Cause:-
Your $OH mount point might be corrupted. You can logged into any users other than "/as sysdba". Because, when you logged into sysdba, you information has been recorded in the audit file.

sqlplus system/xxxx
show parameter audit

audit_file_dest string /u01/app/oracle/admin/ORAPROD/

Check:-
fsck /u01
The current volume is: /dev/fslv00
File system is currently mounted.
Primary superblock is valid.
fsck: Performing read-only processing does not produce dependable results.
*** Phase 1 - Initial inode scan
*** Phase 2 - Process remaining directories
*** Phase 3 - Process remaining files
*** Phase 4 - Check inode allocation map
File system inode map is corrupt (NOT FIXED)
fsck: 0507-278 Cannot continue.
File system is currently mounted.
fsck: Performing read-only processing does not produce dependable results.

Fix:-
Either you can change the audit file location to another mount poing /u02 or shutdown the database and run the fsck on /u01 mount point to fix the corrupted one & start the database.

For change the Audit trial:-

Fix:-
Change the audit_file_dest location to /u02.
alter system audit_file_dest = '/u02/app/oracle/admin/ORAPROD/' scope=both deffered;

Now, you able to connect as "/as sysdba". But, you have to run the fsck on /u01 after bounce the database. This is temporary solution on production database.