控制檔案的恢復方法(二)
控制檔案的通常恢復方法有:
1、從控制檔案自動或二進位制備份中恢復
2、從控制檔案快照備份中恢復
3、控制檔案trace檔案備份中恢復
4、Oracle自動生成的控制檔案指令碼恢復
如下對相關的步驟及語法進行介紹:
2、從控制檔案快照備份中恢復
對資料庫進行一些改動:
SQL> insert into t select * from dba_users;
8 rows created.
SQL> alter system switch logfile;
System altered.
SQL> exit
[@more@]將控制檔案透過OS的mv 或rm命令進行移動或刪除;
[oracle@dbserv test]$ mv control01.ctl control02.ctl control03.ctl /opt/oracle/backups/
[oracle@dbserv test]$ ls
redo01.log redo02.log redo03.log sqlnet.log sysaux01.dbf system01.dbf temp01.dbf undotbs01.dbf users01.dbf
關閉資料庫
SQL> shutdown immediate;
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/opt/oracle/oradata/test/control01.ctl'
ORA-27041: unable to open file
Linux Error: 2: No such file or directory
Additional information: 3
SQL> shutdown force;
SP2-0717: illegal SHUTDOWN option
SQL> shutdown abort;
ORACLE instance shut down.
SQL>
oracle@dbserv ~]$ export ORACLE_SID=test
[oracle@xjtvpay ~]$ rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Jun 15 19:33:42 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount;
RMAN>
RMAN> set DBID=2083742440
executing command: SET DBID
RMAN> restore controlfile from '/opt/oracle/product/10.2.0/dbs/snapcf_test.f';
Starting restore at 15-JUN-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=154 devtype=DISK
channel ORA_DISK_1: copied control file copy
output filename=/opt/oracle/oradata/test/control01.ctl
output filename=/opt/oracle/oradata/test/control02.ctl
output filename=/opt/oracle/oradata/test/control03.ctl
Finished restore at 15-JUN-12
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> restore database;
Starting restore at 15-JUN-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=154 devtype=DISK
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /opt/oracle/oradata/test/system01.dbf
restoring datafile 00002 to /opt/oracle/oradata/test/undotbs01.dbf
restoring datafile 00003 to /opt/oracle/oradata/test/sysaux01.dbf
restoring datafile 00004 to /opt/oracle/oradata/test/users01.dbf
channel ORA_DISK_1: reading from backup piece /opt/backup/full/testfull_TEST_20120610_11
channel ORA_DISK_1: restored backup piece 1
piece handle=/opt/backup/full/testfull_TEST_20120610_11 tag=TESTDB
channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
Finished restore at 15-JUN-12
RMAN> recover database;
Starting recover at 15-JUN-12
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 22 is already on disk as file /opt/backup/1_22_785596008.dbf
archive log thread 1 sequence 23 is already on disk as file /opt/backup/1_23_785596008.dbf
archive log thread 1 sequence 24 is already on disk as file /opt/backup/1_24_785596008.dbf
archive log thread 1 sequence 25 is already on disk as file /opt/backup/1_25_785596008.dbf
archive log thread 1 sequence 26 is already on disk as file /opt/backup/1_26_785596008.dbf
archive log thread 1 sequence 1 is already on disk as file /opt/oracle/oradata/test/redo02.log
archive log thread 1 sequence 2 is already on disk as file /opt/oracle/oradata/test/redo01.log
archive log filename=/opt/backup/1_22_785596008.dbf thread=1 sequence=22
archive log filename=/opt/backup/1_23_785596008.dbf thread=1 sequence=23
archive log filename=/opt/backup/1_24_785596008.dbf thread=1 sequence=24
archive log filename=/opt/backup/1_25_785596008.dbf thread=1 sequence=25
archive log filename=/opt/backup/1_26_785596008.dbf thread=1 sequence=26
archive log filename=/opt/oracle/oradata/test/redo02.log thread=1 sequence=1
archive log filename=/opt/oracle/oradata/test/redo01.log thread=1 sequence=2
media recovery complete, elapsed time: 00:00:35
Finished recover at 15-JUN-12
RMAN> alter database open resetlogs;
database opened
RMAN> exit
Recovery Manager complete.
[oracle@xjtvpay ~]$ sqlplus / as sysdba
SQL> select count(*) from t;
COUNT(*)
----------
16
SQL>
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/18841027/viewspace-1058555/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 與控制檔案有關的恢復(二)
- 與控制檔案有關的恢復
- 【RMAN】如果控制檔案損壞那麼如何恢復?恢復控制檔案的方式有哪幾種?
- [20210225]控制檔案序列號滿的恢復.txt
- 被誤刪的檔案快速恢復方法
- rman恢復控制檔案的一個小錯誤
- U盤檔案被隱藏怎麼恢復 U盤檔案恢復隱藏的方法
- RAC控制檔案恢復(三種不同情況)
- word怎麼恢復儲存前的檔案,word檔案恢復
- 檔案替換後怎麼恢復,恢復被覆蓋的檔案
- 隨身碟檔案被隱藏怎麼恢復 隨身碟檔案恢復隱藏的方法
- u盤檔案變成快捷方式怎麼恢復,恢復U盤檔案的五種方法
- 同名檔案替換怎麼恢復,恢復同名檔案
- 剪下的檔案還能恢復嗎,恢復剪貼丟失的檔案
- 【/proc/檔案淺析】另類辦法恢復資料檔案和控制檔案
- 剪下後的檔案可以恢復嗎?恢復剪下檔案怎麼辦?
- word自動儲存的檔案怎麼恢復,word檔案恢復
- u盤東西誤刪怎麼恢復 恢復u盤檔案的方法
- 電腦裡刪除的檔案怎麼恢復,資料恢復方法大全資料恢復
- win10沒儲存的檔案怎麼恢復_win10檔案未儲存的恢復方法Win10
- Linux下用rm刪除的檔案的恢復方法Linux
- 替換掉的檔案怎麼恢復,兩個方法還原檔案
- Sql Server資料庫檔案丟失的恢復方法SQLServer資料庫
- qq檔案失效怎麼恢復 qq已失效的檔案能不能恢復
- 360粉碎檔案可以恢復嗎,如何恢復360強力刪除的檔案
- oracle控制檔案的損壞或完全丟失的恢復辦法Oracle
- 檔案中勒索恢復
- Git恢復刪除的檔案Git
- uninstall 後的檔案如何恢復
- oracle快速拿到重建控制檔案語句的方法二Oracle
- 行動硬碟刪除的檔案能恢復嗎,怎麼恢復硬碟刪除的檔案硬碟
- win10中mdf檔案被誤刪如何恢復_win10系統mdf檔案被誤刪的恢復方法Win10
- eclipse 恢復誤刪檔案Eclipse
- mysql 從 frm 檔案恢復 table 表結構的3種方法MySql
- 磁碟顯示沒有初始化恢復檔案方法
- XFS檔案系統的備份、恢復、修復
- u盤檔案損壞怎麼恢復資料 u盤恢復損壞資料的有效方法
- git恢復誤刪未提交的檔案Git
- sd卡刪除的檔案如何恢復SD卡