ORA-19625 ORA-27037

来源：互联网发布：两个数据对比的图表编辑：程序博客网时间：2024/06/08 14:21

在进行rman备份时报错

run {

2> allocate channel c1 device type disk;
3> allocate channel c2 device type disk;
4> backup incremental level 0
5> format '/rmanbak/db_full_%U.bkp'
6> tag '2016-07-22-FULL'
7> database plus archivelog;
8> release channel c1;
9> release channel c2;
10> }

using target database control file instead of recovery catalog
allocated channel: c1
channel c1: SID=36 device type=DISK

allocated channel: c2
channel c2: SID=39 device type=DISK

Starting backup at 22-JUL-16
current log archived
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 07/22/2016 05:54:51
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
ORA-19625: error identifying file /home/oracle/1_9_911268083.dbf
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory

Additional information: 3

提示就是找不到这个文件1_9_911268083.dbf
第一个做法是越过去这个，就是查询v$archive_log这个视图。

select sequence# from v$archived_log;

SEQUENCE#
----------
67
237
238
239
240
241

在这里我就可以从237开始

backup archivelog from sequence 237;

这种方法不推荐，下备份还会遇到，可以使用第二方法

crosscheck archivelog all;

delete expired archivelog all;

这样这个没有物理文件的记录就从控制文件中删除了，再执行脚本就没有任何问题了

0 0