oracle備份把日誌錯
備份日誌:
Recovery Manager: Release 10.2.0.4.0 - Production on Thu Jul 30 10:25:07 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: MES (DBID=1757072954)
using target database control file instead of recovery catalog
RMAN> run
2> {
3> allocate channel t1 type 'sbt_tape' connect * parms
4> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
5>
6> allocate channel t2 type 'sbt_tape' connect * parms
7> 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
8>
9> backup database;
10> backup archivelog all delete input;
11> release channel t1;
12> release channel t2;
13> }
14>
allocated channel: t1
channel t1: sid=37 instance=mes2 devtype=SBT_TAPE
channel t1: Data Protection for Oracle: version 5.4.1.0
allocated channel: t2
channel t2: sid=92 instance=mes1 devtype=SBT_TAPE
channel t2: Data Protection for Oracle: version 5.4.1.0
Starting backup at 30-JUL-09
channel t1: starting full datafile backupset
channel t1: specifying datafile(s) in backupset
input datafile fno=00006 name=/dev/rmespdb01
input datafile fno=00005 name=/dev/rmes_undo2_2g
input datafile fno=00004 name=/dev/rmes_users_128m
channel t1: starting piece 1 at 30-JUL-09
channel t2: starting full datafile backupset
channel t2: specifying datafile(s) in backupset
input datafile fno=00003 name=/dev/rmes_saux_1g
input datafile fno=00001 name=/dev/rmes_sys_2g
input datafile fno=00002 name=/dev/rmes_undo1_2g
channel t2: starting piece 1 at 30-JUL-09
channel t2: finished piece 1 at 30-JUL-09
piece handle=udkle2na_1_1 tag=TAG20090730T102511 comment=API Version 2.0,MMS Version 5.4.1.0
channel t2: backup set complete, elapsed time: 00:02:05
channel t2: starting full datafile backupset
channel t2: specifying datafile(s) in backupset
including current control file in backupset
channel t2: starting piece 1 at 30-JUL-09
channel t1: finished piece 1 at 30-JUL-09
piece handle=uckle2o8_1_1 tag=TAG20090730T102511 comment=API Version 2.0,MMS Version 5.4.1.0
channel t1: backup set complete, elapsed time: 00:03:42
channel t1: starting full datafile backupset
channel t1: specifying datafile(s) in backupset
including current SPFILE in backupset
channel t1: starting piece 1 at 30-JUL-09
channel t2: finished piece 1 at 30-JUL-09
piece handle=uekle2r8_1_1 tag=TAG20090730T102511 comment=API Version 2.0,MMS Version 5.4.1.0
channel t2: backup set complete, elapsed time: 00:03:01
channel t1: finished piece 1 at 30-JUL-09
piece handle=ufkle2v6_1_1 tag=TAG20090730T102511 comment=API Version 2.0,MMS Version 5.4.1.0
channel t1: backup set complete, elapsed time: 00:02:50
Finished backup at 30-JUL-09
Starting backup at 30-JUL-09
current log archived
released channel: t1
released channel: t2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 07/30/2009 10:31:52
RMAN-06726: could not locate archivelog /arch1/1_407_673494140.dbf
Recovery Manager complete.
是因為沒有找到歸檔日誌檔案:/arch1/1_407_673494140.dbf
可能被手工刪除了
做一下日誌校驗應該就可以了
處理過程:
su - oracle
$ rman target /
Recovery Manager: Release 10.2.0.4.0 - Production on Thu Jul 30 11:25:37 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: MES (DBID=1757072954)
RMAN> crosscheck archivelog all;
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=48 instance=mes1 devtype=DISK
validation failed for archived log
archive log filename=/arch1/1_407_673494140.dbf recid=846 stamp=693469623
validation failed for archived log
archive log filename=/arch2/2_484_673494140.dbf recid=845 stamp=693461547
validation failed for archived log
archive log filename=/arch2/2_485_673494140.dbf recid=847 stamp=693479529
validation failed for archived log
archive log filename=/arch2/2_486_673494140.dbf recid=848 stamp=693492513
validation failed for archived log
archive log filename=/arch2/2_487_673494140.dbf recid=850 stamp=693505293
validation failed for archived log
archive log filename=/arch2/2_488_673494140.dbf recid=851 stamp=693524283
validation failed for archived log
archive log filename=/arch2/2_489_673494140.dbf recid=852 stamp=693531603
validation failed for archived log
archive log filename=/arch2/2_490_673494140.dbf recid=854 stamp=693544171
validation failed for archived log
archive log filename=/arch2/2_491_673494140.dbf recid=855 stamp=693547866
validation failed for archived log
archive log filename=/arch2/2_492_673494140.dbf recid=856 stamp=693548469
validation failed for archived log
archive log filename=/arch2/2_493_673494140.dbf recid=858 stamp=693564735
validation failed for archived log
archive log filename=/arch2/2_494_673494140.dbf recid=860 stamp=693570712
Crosschecked 12 objects
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/11134849/viewspace-610799/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- oracle rman備份歸檔日誌需要先切換日誌嗎Oracle
- Oracle之備份和清理監聽日誌、告警日誌指令碼Oracle指令碼
- 備份之歸檔重做日誌備份
- 備份歸檔日誌
- sqlserver的日誌備份SQLServer
- oracle自動備份,儲存每天備份日誌的指令碼編寫Oracle指令碼
- 日誌傳送事務日誌備份設定
- RMAN備份歸檔日誌多份 %c
- rman全庫備份備份歸檔日誌檔案
- 備份歸檔日誌檔案
- Oracle使用備份檔案集恢復歸檔日誌Oracle
- Oracle設定多個歸檔路徑生成多份歸檔日誌,Rman備份時也只備份其中的一份歸檔日誌Oracle
- mysql之 xtrabackup原理、備份日誌分析、備份資訊獲取MySql
- MySQL日誌管理,備份和恢復MySql
- 實時備份mysql binlog日誌MySql
- RMAN備份歸檔日誌指令碼指令碼
- onbar的日誌搶救備份
- MySQL 日誌管理、備份與恢復MySql
- ORACLE tsm 備份錯誤Oracle
- rman備份後為什麼要同時備份歸檔日誌
- find 命令刪除冗餘 Nginx 錯誤日誌並實現備份Nginx
- 備份歸檔日誌報錯ORA-19625: crosscheck archivelog allROSHive
- Oracle 12C 新特性:關於歸檔日誌的備份Oracle
- oracle rman不能自動刪除歸檔日誌備份解決Oracle
- Oracle RMAN 不完全恢復(只有資料檔案備份,丟失歸檔日誌備份)Oracle
- 【備份恢復】set newname切換日誌
- LINUX 自動備份程式日誌(shell)Linux
- SQL Server大型事務日誌的備份SQLServer
- FreeBSD系統日誌與備份(轉)
- 冷備份+歸檔日誌的恢復
- mysqldump全量備份+mysqlbinlog二進位制日誌增量備份MySql
- 用RMAN備份歸檔日誌時檢查歸檔日誌是否存在
- 誤刪歸檔日誌除導致備份歸檔日誌失敗
- 歸檔日誌大小 與使用rman 備份後的歸檔日誌產生的備份集大小的關係
- oracle日誌錯誤恢復(轉)Oracle
- Linux伺服器日誌備份到本地Linux伺服器
- YD_顯示RMAN備份資訊及日誌
- HQ_顯示RMAN備份資訊及日誌