You are on page 1of 3

Fix ORA-00257: archiver error. Connect internal only, until freed in Oracle 11G | ...

Pgina 1 de 3

Fix ORA-00257: archiver error.


Connect internal only, until freed
in Oracle 11G
Published on Apr 2 2012
# 91,683 (91,683 reads)
oracle (http://remidian.com/category/oracle/)

When your database hangs with a ORA-00257 error while you notice there is plenty of space in
the /recoveryarea mountpoint youre likely to have reached the maximum size defined by the new
** initialization parameter db_recovery_file_dest_size
(http://docs.oracle.com/cd/B12037_01/server.101/b10755/initparams052.htm). Fast solution is to
simply increase the value for db_recovery_file_dest_size (and after that of course start
archiving)
** 2012-04-02T12:10:; I see now the init parameter db_recovery_file_dest_size is not so new in
fact has been around since Oracle 10.1 OK.

Mon Apr 02 06:01:12 2012


Errors in file /ora/diag/rdbms/$ORACLE_SID/$ORACLE_SID/trace/$ORACLE_SID_arc
0_25342.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 10737418240 bytes is 100.0
0% used, and has 0 remaining bytes available.
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.

SQL> sho parameter db_recovery_file


NAME
----------------------------------------------------------------db_recovery_file_dest
db_recovery_file_dest_size
SQL>

TYPE
VALUE
----------string
/recoveryarea
big integer 10G

http://remidian.com/2012/04/fix-ora-00257-archiver-error-connect-internal-only-until-... 26/09/2015

Fix ORA-00257: archiver error. Connect internal only, until freed in Oracle 11G | ... Pgina 2 de 3

Still plenty of space in the /recoveryarea mountpoint namely 42G however in the databases
archive log dest is getting pretty filled up reaching its defined maxium (calucalated by the os
command du).
Overall space usage in /recoveryarea mountpoint
$ df -h /recoveryarea/$ORACLE_SID/archivelog/
Filesystem
size
used avail capacity
/recoveryarea
98G
55G
42G
57%

Mounted on
/recoveryarea

Space usage in database /recoveryarea directory


$ du -sh /recoveryarea/$ORACLE_SID/archivelog/
10G
/recoveryarea/$ORACLE_SID/archivelog

So in this scenario the quick fix was to issue command below;


SQL> alter system set db_recovery_file_dest_size = 12g;
System altered.
SQL>

Update 2012-07-18T07:54:20+00:00
slightly different error message same cause / solution

http://remidian.com/2012/04/fix-ora-00257-archiver-error-connect-internal-only-until-... 26/09/2015

Fix ORA-00257: archiver error. Connect internal only, until freed in Oracle 11G | ... Pgina 3 de 3

Tue Jul 17 19:57:21 2012


ARC3 started with pid=22, OS id=24912
Errors in file /ora/diag/rdbms/${ORACLE_SID}/${ORACLE_SID}/trace/${ORACLE_SI
D}_ora_24902.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 10066329600 bytes is 100.0
0% used, and has 0 remaining bytes available.
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
************************************************************************
ARCH: Error 19809 Creating archive log file to '/recoveryarea/${ORACLE_SID}/
archivelog/2012_07_17/o1_mf_1_4395_%u_.arc'
Errors in file /ora/diag/rdbms/${ORACLE_SID}/${ORACLE_SID}/trace/${ORACLE_SI
D}_ora_24902.trc:
ORA-16038: log 3 sequence# 4395 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 3 thread 1: '/m003/oradata/${ORACLE_SID}/${ORACLE_SID}
redo3a.log'
ORA-00312: online log 3 thread 1: '/m002/oradata/${ORACLE_SID}/${ORACLE_SID}
redo3b.log'
USER (ospid: 24902): terminating the instance due to error 16038
System state dump requested by (instance=1, osid=24902), summary=[abnormal i
nstance termination].
System State dumped to trace file /ora/diag/rdbms/${ORACLE_SID}/${ORACLE_SI
D}/trace/${ORACLE_SID}_diag_24861.trc
Dumping diagnostic data in directory=[cdmp_20120717195721], requested by (in
stance=1, osid=24902), summary=[abnormal instance termination].
Instance terminated by USER, pid = 24902

http://remidian.com/2012/04/fix-ora-00257-archiver-error-connect-internal-only-until-... 26/09/2015