rac rman備份因歸檔不可訪問出錯RMAN-06059 RMAN-03002 ORA-19625
--linux環境10g的rac庫
--rman RAC備份出錯如下(部分)
Starting Control File and SPFILE Autobackup at 13-SEP-12
piece handle=+DATA/racdb/autobackup/2012_09_13/s_793904799.271.793904805 comment=NONE
Finished Control File and SPFILE Autobackup at 13-SEP-12
Starting Control File and SPFILE Autobackup at 13-SEP-12
piece handle=+DATA/racdb/autobackup/2012_09_13/s_793904799.271.793904805 comment=NONE
Finished Control File and SPFILE Autobackup at 13-SEP-12
sql statement: alter system archive log current
Starting backup at 13-SEP-12
current log archived
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 09/13/2012 17:07:11
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /opt/ora10g/racdb1_arch/1_2_792374929.dbf
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
current log archived
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 09/13/2012 17:07:11
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /opt/ora10g/racdb1_arch/1_2_792374929.dbf
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
--分析,這個原因有3
1、因為手動刪除過歸檔日誌,而未更新相關記錄導致rman無法確定其檔案狀態
解決辦法:crosscheck後刪除過期檔案即可
2、對於rac中的歸檔的備份,需要確定rman可以正常訪問到每個節點的歸檔日誌(可以人為將歸檔拷貝到相關節點目錄)
3、對於rac
解決辦法:修改rman配置parallelism和指令碼(設定的通道每個節點不夠)
參考文件:RMAN Backup Of Archivelog Files On RAC Fails With RMAN-6059 [ID 298119.1]Applies to:
1、因為手動刪除過歸檔日誌,而未更新相關記錄導致rman無法確定其檔案狀態
解決辦法:crosscheck後刪除過期檔案即可
2、對於rac中的歸檔的備份,需要確定rman可以正常訪問到每個節點的歸檔日誌(可以人為將歸檔拷貝到相關節點目錄)
3、對於rac
解決辦法:修改rman配置parallelism和指令碼(設定的通道每個節點不夠)
參考文件:RMAN Backup Of Archivelog Files On RAC Fails With RMAN-6059 [ID 298119.1]Applies to:
Changes
Possible modification of setting for RMAN "parallelism".
Cause
This problem can be caused by changing RMAN parallelism to too low a setting
or initially not setting it high enough such that not ALL the node specific channels are allocated.
Possible modification of setting for RMAN "parallelism".
Cause
This problem can be caused by changing RMAN parallelism to too low a setting
or initially not setting it high enough such that not ALL the node specific channels are allocated.
Solution
Check your rman parallelism setting:
Check your rman parallelism setting:
RMAN>show all;
...
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
...
CONFIGURE DEVICE TYPE DISK PARALLELISM 1;
Make sure parallelism is set to at least the number of channels you're
allocating. For example, if you are issuing this backup command to backup
archivelog files on a two node RAC database:
run {
allocate channel d1 type disk connect 'sys/rac@node1';
allocate channel d2 type disk connect 'sys/rac@node2';
backup archivelog all delete input;
release channel d1;
release channel d2;
}
then set parallelism to 2:
RMAN>CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
If parallelism is not set at least to the number of channels allocated, not all
channels will be used and RMAN will not be able to access all the archivelogs specific to each node.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26143577/viewspace-743390/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- rman備份archivelog出現ORA-19625Hive
- 使用RMAN增量備份處理Dataguard因歸檔丟失造成的gap
- Oracle 11G RAC複製備庫RMAN-03002 RMAN-05501 RMAN-03015 RMAN-03009 RMAN-10038Oracle
- rman開啟備份優化對備份歸檔的影響優化
- RMAN備份整庫和歸檔日誌的方法
- dg丟失歸檔,使用rman增量備份恢復
- Oracle設定多個歸檔路徑生成多份歸檔日誌,Rman備份時也只備份其中的一份歸檔日誌Oracle
- ORACLE NBU調取oracle rman指令碼備份歸檔不自動刪除歸檔Oracle指令碼
- RMAN-ERROR:因為找不到過期和丟失的歸檔日誌而備份失敗Error
- oracle rman備份歸檔日誌需要先切換日誌嗎Oracle
- RMAN刪除歸檔日誌出現RMAN-0813錯誤的處理
- [20190522]rman備份問題.txt
- 資料遷移的時候出現RMAN-03002,RMAN-06026
- 【RMAN】在備庫執行rman備份時報錯RMAN-06820 ORA-17629
- 【RMAN】RMAN備份至ASMASM
- 【RMAN】Oracle12c之後,rman備份Dataguard備端恢復可能出現邏輯錯誤Oracle
- 【備份】RMAN中對控制檔案的幾種備份方法
- RMAN備份概述
- 【RMAN】RMAN的備份保留策略
- oracle 如何不備份已經備份的歸檔Oracle
- 12 使用RMAN備份和恢復檔案
- win10電腦建立系統映像出現錯誤提示裝載的備份卷不可訪問如何解決Win10
- RMAN備份恢復典型案例——RMAN備份&系統變慢
- SQL Server 備份 出現作業系統錯誤 5(拒絕訪問。)SQLServer作業系統
- RMAN備份出現ORA-01801: date format is too long for internal buffer錯誤ORM
- [20190510]rman備份的疑問8.txt
- [20190510]rman備份的疑問7.txt
- [20190509]rman備份的疑問5.txt
- RMAN備份進度
- rman 備份指令碼指令碼
- RMAN的備份原理
- [20221121]rman刪除歸檔日誌問題.txt
- 【RMAN】Oracle中如何備份控制檔案?備份控制檔案的方式有哪幾種?Oracle
- Oracle 12c 使用RMAN搭建物理備庫(RAC to RAC)Oracle
- rman 增量備份恢復
- Oracle RMAN備份實戰Oracle
- Oracle OCP(60):RMAN 備份Oracle
- RMAN備份恢復技巧
- 【rman備份策略】實驗