ORA-09925: Unable to create audit trail file

PROBLEM:

Users are getting below error, while trying to connect to the database.

ERROR:
ORA-09925: Unable to create audit trail file
Linux-ia64 Error: 28: No space left on device
Additional information: 9925
ORA-01075: you are currently logged on

SOLUTION:

The error occurs , because the mount point where audit logs are written is filled.

check the mount point :

[oracle@ram ~]$ df -h

Filesystem    Size     Used     Avail   Use%    Mounted on
/dev/sda2      20G     9.6G      8.7G    53%      /
tmpfs          3.0G    276K      3.0G    1%       /dev/shm
/dev/sda1      194M    105M      79M     58%      /boot
/dev/sda5      45G     40G       3.4G    93%      /u01
.host:/        293G    203G      91G     70%      /mnt/hgfs

[oracle@ram ~]$

We can see that mount point is filled, so database is not able to write audit logs in adump location.

To fix this, clear space from that mount point And make sure free space is available for the audit logs.

Once space is available, user can connect easily.

 

Catch Me On:- Hariprasath Rajaram 

Telegram:https://t.me/joinchat/I_f4DkeGfZuxgMIoJSpQZg LinkedIn:https://www.linkedin.com/in/hariprasathdba Facebook:https://www.facebook.com/HariPrasathdba                       FB Group:https://www.facebook.com/groups/894402327369506/                   FB Page: https://www.facebook.com/dbahariprasath/? Twitter: https://twitter.com/hariprasathdba

ORA-00257:archiver error, connect internal only until freed

PROBLEM:

Application log shows below error and users are unable to connect to the database.

0RA-00257:archiver error, connect internal only until freed
ORA-16014:log 1 sequence# 480 not archived, no available destinations
ORA-00312:online log 1 thread 1:’/data/oradata/orcl/redo01.log’

SOLUTION:

This error comes, when the archive destination is full and there is no space to accommodate new archive logs.

Check archive dest location.

There are different solution for this.

OPTION 1:  Try to delete old archive logs to free up space.

rman target /

delete archivelog all completed before 'sysdate-3';

OPTION 2:  Change the archive log location:

In case you can’t delete the archive logs from existing location, then we can change the archive dest to a new mount point.

SQL> show parameter log_archive_dest_1

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------
log_archive_dest_1                   string      LOCATION=/archive/POCD


SQL> alter system set log_archive_dest_1='LOCATION=/dump/arch' scope=both;

System altered.


SQL> show parameter log_archive_dest_1

NAME                                 TYPE        VALUE
------------------------------------ ----------- --------------------
log_archive_dest_1                  string      LOCATION=/dump/arch
-- Switch logfile

alter system switch logfile;

After implementing any one of the solutions, the database may take few minutes to resume archiving and normal operation.

 

Catch Me On:- Hariprasath Rajaram 

Telegram:https://t.me/joinchat/I_f4DkeGfZuxgMIoJSpQZg LinkedIn:https://www.linkedin.com/in/hari-prasath-aa65bb19/ Facebook:https://www.facebook.com/HariPrasathdba                       FB Group:https://www.facebook.com/groups/894402327369506/                   FB Page: https://www.facebook.com/dbahariprasath/? Twitter: https://twitter.com/hariprasathdba