ORA-00257: archiver error. Connect internal only, until freed.

简介: 今天一上班,登陆测试库,出现ORA-00257: archiver error. Connect internal only, until freed.看alert.

今天一上班,登陆测试库,出现

ORA-00257: archiver error. Connect internal only, until freed.

看alert.log 文件,出现如下:

Sun May 4 11:53:29 2008
ARCH: Archival stopped, error occurred. Will continue retrying
Sun May 4 11:53:29 2008
ORACLE Instance torcl - Archival Error
Sun May 4 11:53:29 2008
ORA-16038: log 1 sequence# 2455 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/torcl/redo01.log'
Sun May 4 11:53:29 2008
Errors in file /u01/app/oracle/admin/torcl/bdump/torcl_arc1_9325.trc:
ORA-16038: log 1 sequence# 2455 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/torcl/redo01.log'
Sun May 4 11:53:30 2008
Errors in file /u01/app/oracle/admin/torcl/bdump/torcl_arc1_9325.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 94.44% used, and has 119342592 remaining bytes available.
************************************************************************
You have following choices to free up space from flash 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.
************************************************************************
Archiver process freed from errors. No longe

很明显是db_recovery_file_dest 的空间满了。

执行rman> delete archivelog until time 'sysdate-1' ;

删除不需要的archive log文件。一切OK。

[@more@]
目录
相关文章
|
7月前
|
SQL Oracle 关系型数据库
WARNING: Too Many Parse Errors With error=911 When Running a JDBC Application Connected to an Oracle 19c database
WARNING: Too Many Parse Errors With error=911 When Running a JDBC Application Connected to an Oracle 19c database (
94 2
|
数据库
ORA-06553: PLS-801: internal error 的解决办法
搜索了一下,原来是把32位的数据库恢复到64位的数据库了。找到解决方案如下
166 0
|
关系型数据库 数据库
ORA-12154: TNS:could not resolve the connect identifier specified
在安装ORACLE安装的时候,报如下错误:ORA-12154: TNS:could not resolve the connect identifier specified。如下图所示: 折腾了很久才找到罪魁祸首:原来在安装数据库时,设置用户密码的时候里面包含了@符号,引起了这个错误,这个错误倒是有点诡异,应该是ORACLE连接DB时就把口令@后面的串当连接字用了。
3025 0
|
Oracle 关系型数据库 数据库
Oracle中Error while performing database login with the XXXdriver; Listener refused the connection with the following error; ORA-12505,TNS:listener does
一次连接数据库怎么也连接不上,查了多方面资料,终于找到答案,总结 首先应该保证数据库的服务启动 在myeclipse的数据库视图中点 右键->new 弹出database driver的窗口, Driver template选择oracle(thin driver), Driver name 输入...
1132 0