A Case of RMAN Exception
阿新 • • 發佈：2018-12-23
[[email protected] data]$ cat 20130226_220001-inc2.log Recovery Manager: Release 11.2.0.1.0 - Production on Tue Feb 26 22:00:01 2013 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. connected to target database: DBTEST (DBID=1193549399) RMAN> run{ 2> sql 'alter system archive log current'; 3> backup 4> incremental level 2 5> format '/db/rmanbak/data/%T_inc2_%U.bkp' 6> tag 'weekly inc2 backup' 7> database plus archivelog; 8> } 9> using target database control file instead of recovery catalog sql statement: alter system archive log current Starting backup at 26-FEB-13 current log archived allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=494 device type=DISK allocated channel: ORA_DISK_2 channel ORA_DISK_2: SID=16 device type=DISK allocated channel: ORA_DISK_3 channel ORA_DISK_3: SID=516 device type=DISK allocated channel: ORA_DISK_4 channel ORA_DISK_4: SID=33 device type=DISK RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of backup plus archivelog command at 02/26/2013 22:00:05 RMAN-06059: expected archived log not found, loss of archived log compromises recoverability ORA-19625: error identifying file /db/oracle/arch/1_1263_800686553.dbf ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Recovery Manager complete.