Sunday, May 20, 2012

ORA-09925



Sometimes, if I’m not paying attention, I do something really silly and it causes me a problem. You can see what I mean in the example below where I was trying to do a STARTUP NOMOUNT before recreating a control file:

SQL> startup nomount
ORA-09925: Unable to create audit trail file
SVR4 Error: 2: No such file or directory
Additional information: 9925
SQL>
 
Fortunately, Oracle seems to have a different error message for every eventuality. This makes mistakes like this easy to rectify. I checked the appropriate line in the database’s parameter file:
 
audit_file_dest='/oracle/app/oracle/product/admin/BORETEST/adump'
 
Then I looked for the directory and saw the problem straight away:
 
BORETEST /oracle/app/oracle/product/admin/BORETEST > pwd
/oracle/app/oracle/product/admin/BORETEST
BORETEST /oracle/app/oracle/product/admin/BORETEST > ls
audit  bdump  cdump  udump
BORETEST /oracle/app/oracle/product/admin/BORETEST >
 
I had created the wrong directory for audit_file_dest so I renamed it:
 
BORETEST /oracle/app/oracle/product/admin/BORETEST > mv audit adump
BORETEST /oracle/app/oracle/product/admin/BORETEST >
 
Then the STARTUP NOMOUNT worked OK:
 
SQL> startup nomount
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown
ORA-01507: database not mounted
 
ORACLE instance shut down.
SQL> startup nomount
ORACLE instance started.
 
Total System Global Area  317423616 bytes
Fixed Size                  2088264 bytes
Variable Size             218104504 bytes
Database Buffers           92274688 bytes
Redo Buffers                4956160 bytes
SQL>

3 comments:

valiantvimal said...

Thanks Andrew for the blog..it helped me a lot..

Anonymous said...

[oracle@RSASPGERP02 ~]$ cd /
[oracle@RSASPGERP02 ~]$ . .bash_profile
[oracle@RSASPGERP02 ~]$ sqlplus / as sysdba

sql*plus:Release 10.2.0.4.0 - production
Error:
ORA-09925:Unable to create audit trail file
Linux-x86_64 Error:28: No space left on device
Additional information :9925
ORA-09925:Unable to create audit trail file
Linux-x86_64 Error:28: No space left on device
Additional information :9925

Enter user-name:_

i need your help guys.....
can you please tell me how to overcome with this issue....its standby archieving problem ,the problem appears when try to connect directly or through telenet
and we try to login directly using oracle user we receving following message and login fail,
"GDM could not write to your authorization file,this could mean that you are out of disk space or that your home directory could not be opened for writting" ,
I DELETED OLD ARCHIVE FILES AND NOW ITS LOGGING IN and everything OK BUT NOW NO NEW ARCHIVEING FILES ARE CREATED
may be iam missing some thing ...
thanks in advance...

Andrew Stuart Reid said...

Is the database still in ARCHIVELOG mode?