Standby上執行RMAN報錯RMAN-10006錯誤處理
環境:Oracle 10g 10.2.0.4 on SuSE 11 + Oracle Data Guard
說明:每天凌晨Standby DB定時只讀開啟供統計用,之後再繼續同步。
故障現象:
執行copy datafile命令報錯RMAN-10006.
如下所示:
RMAN> copy datafile 14 to '/u/oracle/oradata/XXDB22/db2_c037dat03.dbf';
Starting backup at 04/25/2011 10:44:31
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1602 devtype=DISK
channel ORA_DISK_1: starting datafile copy
input datafile fno=00014 name=/u/oracle/oradata/XXDB22/db_c037dat03.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10006: error running SQL statement: select sofar, context, start_time from v$session_longops where (start_time > nvl(:1, sysdate-100) or start_time = nvl(:2, sysdate+100)) and sid = :3 and serial# = :4 and opname like 'RMAN:%' order by start_time desc, context desc
RMAN-10002: ORACLE error: ORA-00000: normal, successful completion
故障解決:
平時甚少會在Standby DB上執行RMAN操作,第一次碰到這樣的報錯。
查詢metalink,發現是oracle的Bug。
Metalink NoteID:1080134.1.
Cause
Unpublished Bug 4230058: FAIL TO CONNECT TO RMAN AFTER PHYSICAL STANDBY IS OPENED READ ONLY
If the standby database is opened readonly and then managed recovery is restarted without bouncing the database, queries against v$session_longops will fail with:
ORA-01219: database not open: queries allowed on fixed tables/views only
RMAN likewise will fail trying to access this view with RMAN-10006 error.
Solution
Restart the standby database after opening it in READ ONLY mode before restarting the Managed Recovery process.
重啟Standby DB後成功執行RMAN命令。
RMAN> copy datafile 14 to '/u/oracle/oradata/XXDB22/db2_c037dat03.dbf';
Starting backup at 04/25/2011 10:55:53
copy datafile 15 to '/u/oracle/oradata/XXDB22/db2_c037dat02.dbf';
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=1627 devtype=DISK
channel ORA_DISK_1: starting datafile copy
input datafile fno=00014 name=/u/oracle/oradata/XXDB22/db_c037dat03.dbf
output filename=/u/oracle/oradata/XXDB22/db2_c037dat03.dbf tag=TAG20110425T105554 recid=53 stamp=749386639
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:01:35
Finished backup at 04/25/2011 10:57:29
Starting Control File and SPFILE Autobackup at 04/25/2011 10:57:29
piece handle=/u/oracle/product/10.2.0/db_1/dbs/c-1988110398-20110425-00 comment=NONE
Finished Control File and SPFILE Autobackup at 04/25/2011 10:57:31
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29154652/viewspace-772248/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Camunda 流程執行錯誤處理ERROR BOUNDARY EVENTError
- 錯誤處理
- Rman報錯ORA-00234: ORA-00202處理
- RMAN刪除歸檔日誌出現RMAN-0813錯誤的處理
- Python錯誤處理Python
- PHP 錯誤處理PHP
- php錯誤處理PHP
- Go 錯誤處理Go
- 錯誤處理:如何通過 error、deferred、panic 等處理錯誤?Error
- DBeaver同時執行多條insert into報錯處理
- idea上執行scala報錯Idea
- flink1.14.0在yarn上執行報錯--類載入錯誤--問題Yarn
- 【RMAN】在備庫執行rman備份時報錯RMAN-06820 ORA-17629
- openGauss 處理錯誤表
- go的錯誤處理Go
- axios 的錯誤處理iOS
- 執行錯誤集
- Android執行出現android Installation failed due to invalid URI! 錯誤處理AndroidAI
- Oracle異常錯誤處理Oracle
- 淺談前端錯誤處理前端
- ORACLE 異常錯誤處理Oracle
- PHP 核心特性 - 錯誤處理PHP
- 15-錯誤處理(Error)Error
- Go語言之錯誤處理Go
- grpc中的錯誤處理RPC
- laravel9 錯誤處理Laravel
- 學習Rust 錯誤處理Rust
- 前端的水平線,錯誤處理和除錯前端除錯
- Python錯誤處理和異常處理(二)Python
- PbootCMS錯誤提示:執行SQL發生錯誤!錯誤:no such column: def1bootSQL
- 七、Spring Boot 錯誤處理原理 & 定製錯誤頁面Spring Boot
- ogg複製程式報ORA-01438錯誤處理
- 【故障處理】如何避免在執行impdp後出現ORA-00001錯誤
- 淺析Node是如何進行錯誤處理的
- node端統一錯誤處理
- node錯誤處理與日誌
- [轉] Scala Try 與錯誤處理
- js錯誤處理權威指北JS
- [譯] 使用 Catcher 處理 Flutter 錯誤Flutter