rman备份出现ORA-19625

这是一个转过来的帖子,今天做RMAN备份的时候正好碰到这个问题。参考了这个解决的办法问题解决了。
因为当时做完以后没有抓图,现在就直接转载这个帖子过来,以备不时之需。
[oracle@sunny stage]$ rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Sun Mar 18 17:21:22 2007
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
connected to target database: ORCL (DBID=1141870147)
 
RMAN> backup archivelog all;
Starting backup at 18-MAR-07
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 03/18/2007 17:52:42
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /u01/1_2_616734317.dbf
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
 
原因在于操作系统下删除了这个归档日志,这个日志还没备份过,rman去备份的时候,找不到这个归档就出错了。可用以下方法解决:
 
RMAN> change archivelog all crosscheck;
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=152 devtype=DISK
validation succeeded for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2007_02_12/o1_mf_1_1_2x01h9c2_.arc recid=1 stam
p=614355305
validation succeeded for archived log
archive log filename=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2007_02_13/o1_mf_1_2_2x147xxt_.arc recid=2 stam
p=614390912
validation succeeded for archived log
......
......
archive log Crosschecked 27 objects

RMAN> backup archivelog all;
Starting backup at 18-MAR-07
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=1 recid=14 stamp=616946466
input archive log thread=1 sequence=3 recid=16 stamp=616947068
input archive log thread=1 sequence=4 recid=17 stamp=617035270
input archive log thread=1 sequence=5 recid=18 stamp=617068230
input archive log thread=1 sequence=6 recid=19 stamp=617214283
input archive log thread=1 sequence=7 recid=20 stamp=617236569
input archive log thread=1 sequence=8 recid=21 stamp=617317844
input archive log thread=1 sequence=9 recid=22 stamp=617365403
input archive log thread=1 sequence=10 recid=23 stamp=617373909
input archive log thread=1 sequence=11 recid=24 stamp=617388719
input archive log thread=1 sequence=12 recid=25 stamp=617546548
input archive log thread=1 sequence=13 recid=26 stamp=617562955
input archive log thread=1 sequence=14 recid=27 stamp=617565160
input archive log thread=1 sequence=15 recid=28 stamp=617565330
channel ORA_DISK_1: starting piece 1 at 18-MAR-07
channel ORA_DISK_1: finished piece 1 at 18-MAR-07
piece handle=/stage/test/ORCL/backupset/2007_03_18/o1_mf_annnn_TAG20070318T175530_2zt34n86_.bkp tag=TAG20070318T175530 c
omment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:36
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=1 recid=1 stamp=614355305
input archive log thread=1 sequence=2 recid=2 stamp=614390912
input archive log thread=1 sequence=3 recid=3 stamp=616178167
input archive log thread=1 sequence=4 recid=4 stamp=616179332
input archive log thread=1 sequence=5 recid=5 stamp=616337492
input archive log thread=1 sequence=6 recid=6 stamp=616456995
input archive log thread=1 sequence=7 recid=7 stamp=616458691
input archive log thread=1 sequence=8 recid=10 stamp=616734185
input archive log thread=1 sequence=9 recid=12 stamp=616734187
input archive log thread=1 sequence=10 recid=11 stamp=616734186
channel ORA_DISK_1: starting piece 1 at 18-MAR-07
channel ORA_DISK_1: finished piece 1 at 18-MAR-07
piece handle=/stage/test/ORCL/backupset/2007_03_18/o1_mf_annnn_TAG20070318T175530_2zt35rxm_.bkp tag=TAG20070318T175530 c
omment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:26
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=1 recid=13 stamp=616734317
channel ORA_DISK_1: starting piece 1 at 18-MAR-07
channel ORA_DISK_1: finished piece 1 at 18-MAR-07
piece handle=/stage/test/ORCL/backupset/2007_03_18/o1_mf_annnn_TAG20070318T175530_2zt36m4w_.bkp tag=TAG20070318T175530 c
omment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 18-MAR-07
备份成功
 
下面是我遇到同样的情况:
 
 
RMAN> backup archivelog all;
Starting backup at 15-FEB-10
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 02/15/2010 03:05:04
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /u01/app/admin/test/oralog1_41_695269311.dbf
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
RMAN> crosscheck archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=418 devtype=DISK
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_41_695269311.dbf recid=64 stamp=705538863
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_42_695269311.dbf recid=65 stamp=705576226
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_43_695269311.dbf recid=66 stamp=705576304
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_44_695269311.dbf recid=67 stamp=705576371
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_45_695269311.dbf recid=68 stamp=705576404
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_46_695269311.dbf recid=69 stamp=705576536
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_47_695269311.dbf recid=70 stamp=705576575
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_48_695269311.dbf recid=71 stamp=705576626
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_49_695269311.dbf recid=72 stamp=705576681
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_50_695269311.dbf recid=73 stamp=705577007
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_51_695269311.dbf recid=74 stamp=705577024
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_52_695269311.dbf recid=75 stamp=705577038
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_53_695269311.dbf recid=76 stamp=705577114
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_54_695269311.dbf recid=77 stamp=705628836
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_55_695269311.dbf recid=78 stamp=706134856
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_56_695269311.dbf recid=79 stamp=706136663
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_57_695269311.dbf recid=80 stamp=706226415
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_58_695269311.dbf recid=81 stamp=706226736
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_59_695269311.dbf recid=82 stamp=706312835
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_60_695269311.dbf recid=83 stamp=706348833
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_61_695269311.dbf recid=84 stamp=706927492
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_62_695269311.dbf recid=85 stamp=706975243
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_63_695269311.dbf recid=86 stamp=706979744
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_64_695269311.dbf recid=87 stamp=706979754
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_65_695269311.dbf recid=88 stamp=706979763
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_66_695269311.dbf recid=89 stamp=706979786
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_67_695269311.dbf recid=90 stamp=707025042
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_68_695269311.dbf recid=91 stamp=707264272
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_69_695269311.dbf recid=92 stamp=707311142
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_70_695269311.dbf recid=93 stamp=707413335
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_71_695269311.dbf recid=94 stamp=707437236
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_72_695269311.dbf recid=95 stamp=707457653
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_73_695269311.dbf recid=96 stamp=707494604
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_74_695269311.dbf recid=97 stamp=707522544
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_75_695269311.dbf recid=98 stamp=707552041
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_76_695269311.dbf recid=99 stamp=707802899
validation failed for archived log
archive log filename=/u01/app/admin/test/oralog1_77_695269311.dbf recid=100 stamp=707805037
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_78_695269311.dbf recid=101 stamp=707864276
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_79_695269311.dbf recid=102 stamp=712492546
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_80_695269311.dbf recid=103 stamp=712492563
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_81_695269311.dbf recid=104 stamp=712492579
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_82_695269311.dbf recid=105 stamp=709947562
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_83_695269311.dbf recid=106 stamp=710303633
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_84_695269311.dbf recid=107 stamp=710648616
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_85_695269311.dbf recid=108 stamp=710996275
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_86_695269311.dbf recid=109 stamp=710996402
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_87_695269311.dbf recid=110 stamp=710996418
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_88_695269311.dbf recid=111 stamp=710996449
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_89_695269311.dbf recid=112 stamp=710996456
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_90_695269311.dbf recid=113 stamp=710996458
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_91_695269311.dbf recid=114 stamp=710996459
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_92_695269311.dbf recid=115 stamp=710996461
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_93_695269311.dbf recid=116 stamp=710996462
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_94_695269311.dbf recid=117 stamp=710996463
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_95_695269311.dbf recid=118 stamp=710996464
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_96_695269311.dbf recid=119 stamp=710996465
validation succeeded for archived log
archive log filename=/u01/app/admin/test/oralog1_97_695269311.dbf recid=120 stamp=710996704
Crosschecked 57 objects

RMAN> backup archivelog all;
Starting backup at 15-FEB-10
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=78 recid=101 stamp=707864276
input archive log thread=1 sequence=79 recid=102 stamp=712492546
input archive log thread=1 sequence=80 recid=103 stamp=712492563
input archive log thread=1 sequence=81 recid=104 stamp=712492579
input archive log thread=1 sequence=82 recid=105 stamp=709947562
input archive log thread=1 sequence=83 recid=106 stamp=710303633
input archive log thread=1 sequence=84 recid=107 stamp=710648616
input archive log thread=1 sequence=85 recid=108 stamp=710996275
input archive log thread=1 sequence=86 recid=109 stamp=710996402
input archive log thread=1 sequence=87 recid=110 stamp=710996418
input archive log thread=1 sequence=88 recid=111 stamp=710996449
input archive log thread=1 sequence=89 recid=112 stamp=710996456
input archive log thread=1 sequence=90 recid=113 stamp=710996458
input archive log thread=1 sequence=91 recid=114 stamp=710996459
input archive log thread=1 sequence=92 recid=115 stamp=710996461
input archive log thread=1 sequence=93 recid=116 stamp=710996462
input archive log thread=1 sequence=94 recid=117 stamp=710996463
input archive log thread=1 sequence=95 recid=118 stamp=710996464
input archive log thread=1 sequence=96 recid=119 stamp=710996465
input archive log thread=1 sequence=97 recid=120 stamp=710996704
input archive log thread=1 sequence=98 recid=121 stamp=710996798
channel ORA_DISK_1: starting piece 1 at 15-FEB-10
channel ORA_DISK_1: finished piece 1 at 15-FEB-10
piece handle=/u01/app/flash_recovery_area/TEST/backupset/2010_02_15/o1_mf_annnn_TAG20100215T030638_5qjlg031_.bkp tag=TAG                                     20100215T030638 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:27
Finished backup at 15-FEB-10
Starting Control File and SPFILE Autobackup at 15-FEB-10
piece handle=/u01/app/flash_recovery_area/TEST/autobackup/2010_02_15/o1_mf_s_710996825_5qjlgt6s_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 15-FEB-10

 

当手工删除了数据库的归档文件后,需要用这个命令进行同步。

(物理上删除了归档日志,但是控制文件并不知道;因此需要交叉检验以同步信息)

crosscheck archivelog all;

当手工删除了RMAN的备份级时,需要使用的是这个命令:
CROSSCHECK BACKUP;

他们的区别是同步的内容不同,一个是同步归档文件的状态,一个是同步RMAN备份信息。

转载另外一篇文章如下:

crosscheck archivelog all

用RMAN的备份中(Veritas等备份软件由于归档日志的异常导致归档日志备份失败)是经常碰到的,解决方法也是非常解单,就是执行2条RMAN的命令:
1. 进入rman
2. connect target /
3. crosscheck archivelog all;
4. delete expired archivelog all;
===========================
这2条命令做什么事情,原理是什么。下面说明一下:
在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 crosscheck 的目的是检查RMAN 的目录以及物理文件,如果物理文件不存在于介质上,将标记为Expired。如果物理文件
存在,将维持Available。如果原先标记为Expired的备份集再次存在于备份介质上(如恢复了损坏的磁盘驱动器后),
crosscheck将把状态重新从Expired标记回Available。
3 crosscheck 输出分两部分。第一部分列出确定存在于备份介质上的所有备份集片,第二部分列出不存在于备份介质上的
备份集片,并将其标记为Expired。当设置备份保存策略后,一个备份过期,crosscheck之后标记为丢弃的备份状态依旧为
availabel,要删除丢弃备份delete obsolete

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/13024285/viewspace-629682/,如需转载,请注明出处,否则将追究法律责任。

转载于:http://blog.itpub.net/13024285/viewspace-629682/

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
信息数据从传统到当代,是一直在变革当中,突如其来的互联网让传统的信息管理看到了革命性的曙光,因为传统信息管理从时效性,还是安全性,还是可操作性等各个方面来讲,遇到了互联网时代才发现能补上自古以来的短板,有效的提升管理的效率和业务水平。传统的管理模式,时间越久管理的内容越多,也需要更多的人来对数据进行整理,并且数据的汇总查询方面效率也是极其的低下,并且数据安全方面永远不会保证安全性能。结合数据内容管理的种种缺点,在互联网时代都可以得到有效的补充。结合先进的互联网技术,开发符合需求的软件,让数据内容管理不管是从录入的及时性,查看的及时性还是汇总分析的及时性,都能让正确率达到最高,管理更加的科学和便捷。本次开发的医院后台管理系统实现了病房管理、病例管理、处方管理、字典管理、公告信息管理、患者管理、药品管理、医生管理、预约医生管理、住院管理、管理员管理等功能。系统用到了关系型数据库中王者MySql作为系统的数据库,有效的对数据进行安全的存储,有效的备份,对数据可靠性方面得到了保证。并且程序也具备程序需求的所有功能,使得操作性还是安全性都大大提高,让医院后台管理系统更能从理念走到现实,确确实实的让人们提升信息处理效率。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值