rman RMAN-06059: expected archived log not found

用rman备份数据库加上plus archivelog 备份归档日志 报这个错误
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 05/05/2014 01:00:04
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
ORA-19625: error identifying file /oracle/PRD/oraarch/PRDarch1_16336_840558852.dbf
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3

1.原因 :归档日志会用 rm 命令定期清除
2.原理(从网上查的资料) :
2.1在controlfile中记录着每一个archivelog的相关信息,当我们在OS下把这些物理文件delete掉或异常变动后,在controlfile中仍然记录着这些archivelog的信息,当我们手工清除archive目录下的文件后,这些记录并没有被我们从controlfile中清除掉,也就是oracle并不知道这些文件已经不存在了!这时候我们要做手工的清除。 crosscheck archivelog all;的作用就是检查控制文件和实际物理文件的差别。
delete expired archivelog all;就是同步控制文件的信息和实际物理文件的信息。 如果单独执行crosscheck而没有执行delete那么备份还是失败的,原因是那些控制文件的信息和实际的信息还是不同。 crosscheck backupset crosscheck backupset 是检查备份集和实际的文件 1 备份集有两种状态A(Available,RMAN认为该项存在于备份介质上)X(Expired,备份存在于控制文件或恢复目录中,但
是并没有物理存在于备份介质上)
2.2 crosscheck 的目的是检查RMAN 的目录以及物理文件,如果物理文件不存在于介质上,将标记为Expired。如果物理文件
存在,将维持Available。如果原先标记为Expired的备份集再次存在于备份介质上(如恢复了损坏的磁盘驱动器后),
crosscheck将把状态重新从Expired标记回Available。
3.解决方法:在脚本中加入
RMAN> crosscheck archivelog all;
RMAN> delete expired archivelog all;

参考博文:http://blog.chinaunix.net/uid-27570589-id-4237145.html

时间: 2024-10-18 01:13:47

rman RMAN-06059: expected archived log not found的相关文章

RMAN-06059: expected archived log not found,ORA-19625

RMAN> backup  database format='/oracle_rman/%d_%s.dbf' plus archivelog; Starting backup at 31-7月 -11 current log archived using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid=137 devtype

RMAN-06059: expected archived log not found, loss of archived log compromises recoverability ORA-19625: error identifying file /home/Oracle/PROD/1_2_844469007.dbf

rman备份archivelog时出现以下错误: RMAN> backup archivelog all delete input; Starting backup at 14-APR-14 current log archived using channel ORA_DISK_1 using channel ORA_DISK_2 RMAN-00571: =========================================================== RMAN-00569:

DG环境RMAN删除归档报错RMAN-08137: archived log not deleted

Oracle 12C DG环境,备库归档目录告警,查看crontab脚本,发现有删除操作,保持两天的,后手动执行,查看具体报错原因: RMAN> delete noprompt expired archivelog all; released channel: ORA_DISK_1allocated channel: ORA_DISK_1channel ORA_DISK_1: SID=5408 device type=DISKspecification does not match any ar

12.2备库rman使用delete删除归档日志报错RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

问题: 客户环境12.2 dg备库环境,定时清理归档脚本并未正常清理归档日志文件. 观察日志可以发现存在如下信息 RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process . 一般情况下,如果在备库环境或者主库环境,配置归档清理测量后,DG环境未应用归档将不允许删除. 本次排查RMAN清理归档策略默认,且无法删除的归档日志在DG视图v$archived_log 中ap

(转)RMAN-06054: media recovery requesting unknown archived log for thread...

转自:http://blog.itpub.net/29800581/viewspace-1307267/ 使用rman执行recover database 的时候出现RMAN-06054的错误提示: RMAN> recover database; Starting recover at 21-OCT-14 using channel ORA_DISK_1 starting media recovery archived log for thread 1 with sequence 1 is al

Could not find archived log for sequence 1 thread 2 under default destinations SQL

ERROR   OGG-00446  Oracle GoldenGate Capture for Oracle, extjms2.prm:  Could not find archived log for sequence 1 thread 2 under default destinations SQL <SELECT  name    FROM v$archived_log   WHERE sequence# = :ora_seq_no AND         thread# = :ora_

【oracle】oracledba14 archived log files

The loss of which two types of files may require a recovery with the RESETLOGS option?(Choose two.) A. control files B. password file C. archived log files D. system-critical data files for which all the redo entries are present E. non-system-critica

【oracle】oracledba15 To uniquely identify the archived log files for each incarnation of the databas

You are using Oracle Database 10g. The log LOG_ARCHIVE_FORMAT pa rameter is set to 'LOG%t_%_s_%r.dbf'. Why is %r used in the file name format? A. To uniquely identify the archived log files with the restore operation. B. To uniquely identify the arch

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

RMAN-08137 When deleting archivelogs even when Streams CAPTURE does not require them [ID 1079953.1] In this Document  Symptoms  Changes  Cause  Solution  References Symptoms Applies To: 11gR1-11gR2 RMAN is unable to delete archive logs from database