最近在學習rman,恢復的時候報錯,大家看看,怎麼解決
最近在學習rman,恢復的時候報錯,大家看看,怎麼解決
SQL> alter database open ;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-19901: database needs more recovery to create new incarnation
網上關於ora-19901的處理好少啊
SQL> alter database open ;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-19901: database needs more recovery to create new incarnation
網上關於ora-19901的處理好少啊
---------------------------
首先感謝大家的幫助,
1、sqlplus下
recover database until cancel;
2、rman下
restore database;
recover database;
這個方法不行,一,我沒有全表備份,二,我備份了spfile,controlfile,archivelog,spfile和controlfile我都恢復了,沒有異常的問題,主要是archivelog file ,我之前做過backup archivelog all delete input ;後來又重新備份的時候還是這個語句,我在想是不是第一次備份刪除了日誌檔案,第二次備份的時候刪除的檔案找不到了,所以恢復的時候出現問題了??
恢復的時候部分錯誤資訊:
RMAN-03002: failure of recover command at 06/03/2011 09:09:32
RMAN-06053: unable to perform. media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 2429 lowscn 997181116 found to restore
RMAN-06025: no backup of log thread 1 seq 2428 lowscn 997173052 found to restore
RMAN-06025: no backup of log thread 1 seq 2427 lowscn 997165018 found to restore
RMAN-06025: no backup of log thread 1 seq 2426 lowscn 997156390 found to restore
RMAN-06025: no backup of log thread 1 seq 2425 lowscn 997148327 found to restore
RMAN-06025: no backup of log thread 1 seq 2424 lowscn 997142921 found to restore
RMAN-06025: no backup of log thread 1 seq 2423 lowscn 997139905 found to restore
RMAN-06025: no backup of log thread 1 seq 2422 lowscn 997137418 found to restore
RMAN-06025: no backup of log thread 1 seq 2421 lowscn 997132151 found to restore
RMAN-06025: no backup of log thread 1 seq 2420 lowscn 997122744 found to restore
RMAN-06025: no backup of log thread 1 seq 2419 lowscn 997114426 found to restore
RMAN-06025: no backup of log thread 1 seq 2418 lowscn 997105934 found to restore
RMAN-06025: no backup of log thread 1 seq 2417 lowscn 997097451 found to restore
RMAN-06025: no backup of log thread 1 seq 2416 lowscn 997090221 found to restore
RMAN-06025: no backup of log thread 1 seq 2415 lowscn 997083259 found to restore
RMAN-06025: no backup of log thread 1 seq 2414 lowscn 997080987 found to restore
RMAN-06025: no backup of log thread 1 seq 2413 lowscn 997072936 found to restore
RMAN-06025: no backup of log thread 1 seq 2412 lowscn 997065308 found to restore
RMAN-06025: no backup of log thread 1 seq 2411 lowscn 997057305 found to restore
RMAN-06025: no backup of log thread 1 seq 2410 lowscn 997049490 found to restore
RMAN-06025: no backup of log thread 1 seq 2409 lowscn 997041050 found to restore
RMAN-06025: no backup of log thread 1 seq 2408 lowscn 997032588 found to restore
RMAN-06025: no backup of log thread 1 seq 2407 lowscn 997029224 found to restore
RMAN-06025: no backup of log thread 1 seq 2406 lowscn 997025167 found to restore
RMAN-06025: no backup of log thread 1 seq 2405 lowscn 997017988 found to restore
RMAN-06025: no backup of log thread 1 seq 2404 lowscn 997010350 found to restore
RMAN-06025: no backup of log thread 1 seq 2403 lowscn 997002302 found to restore
RMAN-06025: no backup of log thread 1 seq 2402 lowscn 996994913 found to restore
RMAN-06025: no backup of log thread 1 seq 2401 lowscn 996991338 found to restore
1、sqlplus下
recover database until cancel;
2、rman下
restore database;
recover database;
這個方法不行,一,我沒有全表備份,二,我備份了spfile,controlfile,archivelog,spfile和controlfile我都恢復了,沒有異常的問題,主要是archivelog file ,我之前做過backup archivelog all delete input ;後來又重新備份的時候還是這個語句,我在想是不是第一次備份刪除了日誌檔案,第二次備份的時候刪除的檔案找不到了,所以恢復的時候出現問題了??
恢復的時候部分錯誤資訊:
RMAN-03002: failure of recover command at 06/03/2011 09:09:32
RMAN-06053: unable to perform. media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 2429 lowscn 997181116 found to restore
RMAN-06025: no backup of log thread 1 seq 2428 lowscn 997173052 found to restore
RMAN-06025: no backup of log thread 1 seq 2427 lowscn 997165018 found to restore
RMAN-06025: no backup of log thread 1 seq 2426 lowscn 997156390 found to restore
RMAN-06025: no backup of log thread 1 seq 2425 lowscn 997148327 found to restore
RMAN-06025: no backup of log thread 1 seq 2424 lowscn 997142921 found to restore
RMAN-06025: no backup of log thread 1 seq 2423 lowscn 997139905 found to restore
RMAN-06025: no backup of log thread 1 seq 2422 lowscn 997137418 found to restore
RMAN-06025: no backup of log thread 1 seq 2421 lowscn 997132151 found to restore
RMAN-06025: no backup of log thread 1 seq 2420 lowscn 997122744 found to restore
RMAN-06025: no backup of log thread 1 seq 2419 lowscn 997114426 found to restore
RMAN-06025: no backup of log thread 1 seq 2418 lowscn 997105934 found to restore
RMAN-06025: no backup of log thread 1 seq 2417 lowscn 997097451 found to restore
RMAN-06025: no backup of log thread 1 seq 2416 lowscn 997090221 found to restore
RMAN-06025: no backup of log thread 1 seq 2415 lowscn 997083259 found to restore
RMAN-06025: no backup of log thread 1 seq 2414 lowscn 997080987 found to restore
RMAN-06025: no backup of log thread 1 seq 2413 lowscn 997072936 found to restore
RMAN-06025: no backup of log thread 1 seq 2412 lowscn 997065308 found to restore
RMAN-06025: no backup of log thread 1 seq 2411 lowscn 997057305 found to restore
RMAN-06025: no backup of log thread 1 seq 2410 lowscn 997049490 found to restore
RMAN-06025: no backup of log thread 1 seq 2409 lowscn 997041050 found to restore
RMAN-06025: no backup of log thread 1 seq 2408 lowscn 997032588 found to restore
RMAN-06025: no backup of log thread 1 seq 2407 lowscn 997029224 found to restore
RMAN-06025: no backup of log thread 1 seq 2406 lowscn 997025167 found to restore
RMAN-06025: no backup of log thread 1 seq 2405 lowscn 997017988 found to restore
RMAN-06025: no backup of log thread 1 seq 2404 lowscn 997010350 found to restore
RMAN-06025: no backup of log thread 1 seq 2403 lowscn 997002302 found to restore
RMAN-06025: no backup of log thread 1 seq 2402 lowscn 996994913 found to restore
RMAN-06025: no backup of log thread 1 seq 2401 lowscn 996991338 found to restore
------------------------
sqlplus下
1、SQL> recover database using backup controlfile until cancel;
根據提示輸入 redo.log檔案的目錄,如果redo.log檔案不止一個,可以一個一個的嘗試,直到出現以下兩句話:
Log applied.
Media recovery complete.
2、SQL> alter database open resetlogs;
Database altered.
---------
1、SQL> recover database using backup controlfile until cancel;
根據提示輸入 redo.log檔案的目錄,如果redo.log檔案不止一個,可以一個一個的嘗試,直到出現以下兩句話:
Log applied.
Media recovery complete.
2、SQL> alter database open resetlogs;
Database altered.
---------
感謝lks2004,也感謝大家的幫助,
問題按照lks2004的方法解決了,
想再問一下,我從最近的歸檔日誌往回試,為什麼最近的不行,一直到某一個就可以了呢??
------------
問題按照lks2004的方法解決了,
想再問一下,我從最近的歸檔日誌往回試,為什麼最近的不行,一直到某一個就可以了呢??
------------
不太清楚,
根據猜想,應該是控制檔案也需要用最近的才行,因為控制檔案決定了資料庫某一時刻的資料庫各種檔案資訊。需要控制檔案和資料檔案,日誌檔案同步,否則就恢復不了。
根據猜想,應該是控制檔案也需要用最近的才行,因為控制檔案決定了資料庫某一時刻的資料庫各種檔案資訊。需要控制檔案和資料檔案,日誌檔案同步,否則就恢復不了。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/196700/viewspace-703371/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- rman恢復的時候可以使用LASTSCNAST
- Git操作檔案的時候手賤了,怎麼恢復?Git
- 解決vue使用Sass時候的報錯問題Vue
- 電腦404頁面怎麼恢復 404錯誤頁面怎麼解決
- Prometheus 告警恢復時,怎麼獲取恢復時的值?Prometheus
- mongodb find報錯怎麼解決MongoDB
- 徹底解決rman恢復碰到ora-01152錯
- 異機恢復RMAN-05517解決方法
- mysql匯入報錯怎麼解決?MySql
- RMAN學習小結1:不完全恢復
- rman資料備份恢復學習筆記筆記
- 10g新特性:rman恢復時候資料檔案的自動建立
- 刪除的微信聊天記錄怎麼恢復?(已解決)
- rman映象備份全庫的時候報ora-00600錯誤。
- rman恢復到指定時間點
- npm publish 釋出一個 Angular 庫的時候報錯以及解決方法NPMAngular
- Oracle rman 備份與恢復 臨時表空間的檔案問題解決Oracle
- RMAN恢復 執行重要檔案RMAN恢復
- 鍵盤按鍵錯亂怎麼恢復 電腦鍵盤字母錯亂三種解決方法
- rman恢復時跳過資料檔案,進行恢復
- RMAN恢復 執行不重要檔案的RMAN恢復
- win10 恢復選項沒有該怎麼辦 win10沒有恢復選項怎麼解決Win10
- 重要問題,連結mysql錯誤,怎麼解決啊,謝謝大家MySql
- 大家幫幫忙,看看這個SQL怎麼寫!SQL
- 顯示卡什麼時候會降價 顯示卡降價恢復正常時間分析
- 當資料檔案表空間丟失的時候怎麼恢復該資料檔案
- rman恢復控制檔案的一個小錯誤
- RMAN-06026報錯解決方法
- 機器什麼時候能夠學習?
- 【RMAN】表空間基於時間點的RMAN恢復-TSPITR
- rman恢復--丟失控制檔案的恢復
- 什麼是遷移學習?什麼時候使用遷移學習?遷移學習
- 建立cache group 時遇到 錯誤5120 時候的解決方案
- U盤分割槽刪除了怎麼恢復資料?快來看看吧
- 【RMAN】RMAN跨版本恢復(上)
- 【RMAN】RMAN跨版本恢復(中)
- win10沒有恢復選項怎麼辦 win10開機無法進入恢復模式怎麼解決Win10模式
- rsync 客戶端同步的時候報錯客戶端