Professional Documents
Culture Documents
Pgina 1 de 3
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.
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
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
http://remidian.com/2012/04/fix-ora-00257-archiver-error-connect-internal-only-until-... 26/09/2015