全数据库的完全恢复

1、1 全数据库的完全恢复   run    allocate channel c11 type disk;      allocate channel c12 type disk;      allocate channel c21 type 'sbt_tape'      allocate channel c22 type 'sbt_tape' restore co

2、ntrolfile; alter database mount;      restore database;                   recover database;                

3、60;   sql "alter database open"           release channel c11;      release channel c12;      release channel c21;      release channel c22;   &#

4、160; 恢复步骤如下：$ svrmgrlsvrmgr> connect internalsvrmgr> startup nomount$ rmanprod recdbs.rcv >>rec.log &$ tail f rec.log    # 观察日志     使用以上以上的全备份可以对数据库进行全库的恢复，并可以在恢复脚本中直接实现数据库归档日志的应用，将数据库自动恢复到最近的日志记录的状态。    注意：恢复时如果有需要应用很多归档日志，则应用该日志时时间会

5、比较长，一定要耐心等待。全恢复日志如下：  RMAN-00569: =error message stack follows=RMAN-00554: initialization of internal recovery manager package failedRMAN-04005: error from target database: ORA-01034: ORACLE not available  RMAN-06005: connected to target database: FJTESTRMAN-06008: connected to r

6、ecovery catalog database RMAN> run2> 3>   allocate channel c11 type disk;4>   allocate channel c12 type disk;5>   allocate channel c21 type 'sbt_tape'6>   allocate channel c22 type 'sbt_tape'7>   restore data

7、base;8>   recover database;9>   sql "alter database open"10>   release channel c11;11>   release channel c12;12>   release channel c21;13>   release channel c22;14> 15> RMAN-03022: compiling command: alloca

8、teRMAN-03023: executing command: allocateRMAN-08030: allocated channel: c11RMAN-08500: channel c11: sid=13 devtype=DISK RMAN-03022: compiling command: allocateRMAN-03023: executing command: allocateRMAN-08030: allocated channel: c12RMAN-08500: channel c12: sid=14 devtype=DISK RMAN-03022: c

9、ompiling command: allocateRMAN-03023: executing command: allocateRMAN-08030: allocated channel: c21RMAN-08500: channel c21: sid=15 devtype=SBT_TAPE RMAN-03022: compiling command: allocateRMAN-03023: executing command: allocateRMAN-08030: allocated channel: c22RMAN-08500: channel c22: sid=17 dev

10、type=SBT_TAPE RMAN-03022: compiling command: set RMAN-03022: compiling command: restoreRMAN-03025: performing implicit partial resync of recovery catalogRMAN-03023: executing command: partial resyncRMAN-08003: starting partial resync of recovery catalogRMAN-08005: partial resync complete&#

11、160;RMAN-03022: compiling command: IRESTORERMAN-03023: executing command: IRESTORERMAN-08016: channel c21: starting datafile backupset restoreRMAN-08502: set_count=28 set_stamp=402253457RMAN-08016: channel c22: starting datafile backupset restoreRMAN-08502: set_count=29 set_stamp=402253577RMAN-08019

12、: channel c21: restoring datafile 1RMAN-08509: destination for restore of datafile 1: /dev/vx/rdsk/datadg/system01RMAN-08019: channel c22: restoring datafile 3RMAN-08509: destination for restore of datafile 3: /dev/vx/rdsk/datadg/tempaRMAN-08019: channel c21: restoring datafile 2RMAN-08509: destinat

13、ion for restore of datafile 2: /dev/vx/rdsk/datadg/rbsaRMAN-08019: channel c22: restoring datafile 16RMAN-08509: destination for restore of datafile 16: /dev/vx/rdsk/datadg/t3s200n1RMAN-08023: channel c21: restored backup piece 1RMAN-08511: piece handle=dbf_28_402253457_1 params=NULLRMAN-08024: chan

14、nel c21: restore completeRMAN-08016: channel c21: starting datafile backupset restoreRMAN-08502: set_count=31 set_stamp=402253614RMAN-08019: channel c21: restoring datafile 4RMAN-08509: destination for restore of datafile 4: /dev/vx/rdsk/datadg/toolsRMAN-08019: channel c21: restoring datafile 7RMAN-

15、08509: destination for restore of datafile 7: /dev/vx/rdsk/datadg/tempbRMAN-08023: channel c22: restored backup piece 1RMAN-08511: piece handle=dbf_29_402253577_1 params=NULLRMAN-08024: channel c22: restore completeRMAN-08016: channel c22: starting datafile backupset restoreRMAN-08502: set_count=32

16、set_stamp=402253679RMAN-08019: channel c22: restoring datafile 5RMAN-08509: destination for restore of datafile 5: /dev/vx/rdsk/datadg/usersRMAN-08019: channel c22: restoring datafile 13RMAN-08509: destination for restore of datafile 13: /dev/vx/rdsk/datadg/t3s1n1RMAN-08023: channel c21: restored ba

17、ckup piece 1RMAN-08511: piece handle=dbf_31_402253614_1 params=NULLRMAN-08024: channel c21: restore completeRMAN-08016: channel c21: starting datafile backupset restoreRMAN-08502: set_count=30 set_stamp=402253614RMAN-08019: channel c21: restoring datafile 6RMAN-08509: destination for restore of data

18、file 6: /dev/vx/rdsk/datadg/rbsbRMAN-08019: channel c21: restoring datafile 17RMAN-08509: destination for restore of datafile 17: /dev/vx/rdsk/datadg/t2s200n8RMAN-08023: channel c21: restored backup piece 1RMAN-08511: piece handle=dbf_30_402253614_1 params=NULLRMAN-08024: channel c21: restore comple

19、teRMAN-08016: channel c21: starting datafile backupset restoreRMAN-08502: set_count=26 set_stamp=402253457RMAN-08019: channel c21: restoring datafile 8RMAN-08509: destination for restore of datafile 8: /dev/vx/rdsk/datadg/system02RMAN-08019: channel c21: restoring datafile 10RMAN-08509: destination

20、for restore of datafile 10: /dev/vx/rdsk/datadg/t3s500n2RMAN-08023: channel c22: restored backup piece 1RMAN-08511: piece handle=dbf_32_402253679_1 params=NULLRMAN-08024: channel c22: restore completeRMAN-08016: channel c22: starting datafile backupset restoreRMAN-08502: set_count=25 set_stamp=40225

21、3457RMAN-08023: channel c21: restored backup piece 1RMAN-08511: piece handle=dbf_26_402253457_1 params=NULLRMAN-08024: channel c21: restore completeRMAN-08016: channel c21: starting datafile backupset restoreRMAN-08502: set_count=27 set_stamp=402253457RMAN-08019: channel c22: restoring datafile 9RMA

22、N-08509: destination for restore of datafile 9: /dev/vx/rdsk/datadg/t2s500n2RMAN-08019: channel c21: restoring datafile 11RMAN-08509: destination for restore of datafile 11: /dev/vx/rdsk/datadg/t2s500n10RMAN-08019: channel c22: restoring datafile 12RMAN-08509: destination for restore of datafile 12:

23、 /dev/vx/rdsk/datadg/t3s500n1RMAN-08019: channel c21: restoring datafile 14RMAN-08509: destination for restore of datafile 14: /dev/vx/rdsk/datadg/t2s200n10RMAN-08023: channel c22: restored backup piece 1RMAN-08511: piece handle=dbf_25_402253457_1 params=NULLRMAN-08024: channel c22: restore complete

24、RMAN-08016: channel c22: starting datafile backupset restoreRMAN-08502: set_count=33 set_stamp=402253726RMAN-08019: channel c22: restoring datafile 15RMAN-08509: destination for restore of datafile 15: /dev/vx/rdsk/datadg/t2s1n1RMAN-08023: channel c21: restored backup piece 1RMAN-08511: piece handle

25、=dbf_27_402253457_1 params=NULLRMAN-08024: channel c21: restore completeRMAN-08023: channel c22: restored backup piece 1RMAN-08511: piece handle=dbf_33_402253726_1 params=NULLRMAN-08024: channel c22: restore completeRMAN-03023: executing command: partial resyncRMAN-08003: starting partial resync of

26、recovery catalogRMAN-08005: partial resync complete RMAN-03022: compiling command: recover RMAN-03022: compiling command: recover(1) RMAN-03022: compiling command: recover(2) RMAN-03022: compiling command: recover(3)RMAN-03023: executing command: recover(3)RMAN-08054: starting me

27、dia recoveryRMAN-08515: archivelog filename=/archlog/arch2_1.log thread=2 sequence=1RMAN-08515: archivelog filename=/archlog/arch1_1.log thread=1 sequence=1RMAN-08515: archivelog filename=/archlog/arch2_2.log thread=2 sequence=2RMAN-08515: archivelog filename=/archlog/arch2_3.log thread=2 sequence=3

28、RMAN-08515: archivelog filename=/archlog/arch2_4.log thread=2 sequence=4RMAN-08515: archivelog filename=/archlog/arch1_2.log thread=1 sequence=2RMAN-08515: archivelog filename=/archlog/arch2_5.log thread=2 sequence=5RMAN-08515: archivelog filename=/archlog/arch2_6.log thread=2 sequence=6RMAN-08515:

29、archivelog filename=/archlog/arch1_3.log thread=1 sequence=3RMAN-08515: archivelog filename=/archlog/arch2_7.log thread=2 sequence=7RMAN-08515: archivelog filename=/archlog/arch2_8.log thread=2 sequence=8RMAN-08515: archivelog filename=/archlog/arch2_9.log thread=2 sequence=9RMAN-08055: media recove

30、ry complete RMAN-03022: compiling command: recover(4) RMAN-03022: compiling command: sqlRMAN-06162: sql statement: alter database openRMAN-03023: executing command: sqlRMAN-03026: error recovery releasing channel resourcesRMAN-08031: released channel: c12RMAN-08031: released channel: c11RM

31、AN-08031: released channel: c21RMAN-08031: released channel: c22 Recovery Manager complete.以下将不注明恢复日志。2 表空间的恢复run   allocate channel c11 type disk;      allocate channel c12 type disk;      allocate channel c21 type 'sbt_tape' 

32、     allocate channel c22 type 'sbt_tape'      sql "alter tablespace test_tbs1 offline immediate"   # 使表空间离线      restore tablespace test_tbs1;          

33、;     # 物理恢复表空间      recover tablespace test_tbs1;               # 逻辑恢复表空间（应用日志）      sql "alter tablespace test_tbs1 online"    &

34、#160;         # 使表空间在线      release channel c11;      release channel c12;      release channel c21;      release channel c22;     表空间恢复分为离线

35、和在线两种，数据库在线时，如果某表空间发生损坏，可以进行在线的表空间恢复，该任务不会影响数据库其他表空间的正常运行。    当系统表空间损坏，导致数据库不能正常运行，因此需离线恢复系统表空间。测试步骤如下：在线恢复某应用表空间a)    破坏某表空间数据文件$ cd /dev/vx/rdsk/datadg$ dd if=data01 of=data02 bs=10kb)    对该数据文件进行操作svrmgr> alter system check datafiles;svrmgr> sele

36、ct file#,status,error from v$datafile_header如果发现错误，则该数据库文件已经被损坏。c)    恢复该表空间svrmgr> alter tablespace test_tbs1 offline;$ rmanprod rectbs.rcv >> rec2.log &svrmgr> select file#,status,error from v$datafile_header在使用上命令查看恢复情况，如果所有的数据文件状态都为“online”，即表明本恢复成功。3 系统表空间的恢复（数据文件

37、的恢复情况）：  run   allocate channel c11 type disk;     allocate channel c12 type disk;     allocate channel c21 type 'sbt_tape'     allocate channel c22 type 'sbt_tape'     restore tablespace s

38、ystem;     recover tablespace system;     sql "alter database open"     release channel c11;     release channel c12;     release channel c21;     release channel c22;

39、60;     在对系统表空间进行恢复时，由于数据库系统运行已经不正常，因此必须使OPS某线程（本例中为test-host2上线程2）在mount状态，然后执行以上恢复脚本。   步骤如下：   $ svrmgr> startup mount;   $ rmanprod  rectbs.rcv >>rec2.log恢复日志与在线恢复表空间基本相同。 4 全库物理恢复，逻辑恢复至某时刻run  allocate channel c11 type disk;&#

40、160; allocate channel c12 type disk;  allocate channel c21 type 'sbt_tape'  allocate channel c22 type 'sbt_tape'  restore database;         # 执行数据库全库的物理恢复  set until time 'Jul 05 2000 11:00:00'  recover database

41、;         # 执行数据库全库的逻辑恢复，恢复到该时刻的状态  sql "alter database open"  release channel c11;  release channel c12;  release channel c21;  release channel c22;    按时间点恢复的情况使用于：数据库发生逻辑错误，例如在7月6日发生了逻辑错误，即表中有了错误的内容而非数据库系统故障

42、，需要恢复到7月5日11：00的状态。 5 物理恢复至某时间点，然后逻辑恢复到该时刻：run  allocate channel c11 type disk;  allocate channel c12 type disk;  allocate channel c21 type 'sbt_tape'  allocate channel c22 type 'sbt_tape'  set until time 'Jul 05 2000 11:00:00'  restore data

43、base;         # 执行数据库全库的物理恢复，恢复到2000/07/05 11：00  recover database;         # 执行数据库全库的逻辑恢复，恢复到2000/07/05 11：00  sql "alter database open"     # 打开数据库  release channel c11;

44、0; release channel c12;  release channel c21;  release channel c22;    按时间点恢复的情况使用于： 使用当前时间的备份版本不可用，必须使用前一次的备份版本进行恢复，例如在7月6日备份的磁带发现故障，即磁带中有了错误块，并且数据库系统发生故障，需马上恢复到正常运行状态，本例中即实现了恢复至7月5日11：00的状态。 6 按LOGSEQ的恢复到某日志，然后逻辑恢复到当前时刻run  allocate channel c11 type disk;  a

45、llocate channel c12 type disk;  allocate channel c21 type 'sbt_tape'  allocate channel c22 type 'sbt_tape'  set until logseq 10 thread 2;  restore database;  set until time 'SYSDATE'  recover database;  sql "alter database open"

46、60; release channel c11;  release channel c12;  release channel c21;  release channel c22;    使用如上脚本可用于将数据库恢复到应用某一个日志，恢复到某一日志与恢复到某时间点的结果基本相同，应用场合也基本相同。 7 数据文件恢复到另外一个数据文件的恢复run  allocate channel c11 type disk;  allocate channel c12 type disk;  allocate channel c21 type 'sbt_tape'  allocate channel c22 type 'sbt_tape'  sql “alter tablespace test_tbs1 offline immediate”;  set newname f