RESETLOGS后没有备份情况下的数据恢复
2007-05-08 12:10:33 来源:WEB开发网核心提示: del f:est*.dbfcopy f:est*.arc f:coolarchb_ccopy f:est1ctl.ctl f:coolctl_ccopy f:coolcoola*.dbf f:estcopy f:coolctl_actl.ctl f:est1copy f:coolctl_
del f: est*.dbf
copy f: est*.arc f:coolarchb_c
copy f: est1ctl.ctl f:coolctl_c
copy f:coolcoola*.dbf f: est
copy f:coolctl_actl.ctl f: est1
copy f:coolctl_actl.ctl f: est2
copy f:coolctl_actl.ctl f: est3
(16)以SYSDBA身份登录,执行从时刻A到时刻B的基于时间点的不完全媒体恢复,因为媒体恢复过程使用时刻A的控制文件,所以要加上using backup controlfile子句。该步骤类似于步骤(10)。
conn /@test as sysdba
startup mount
recover database until time '2002-10-04:09:18:52' using backup controlfile;
(17)该步骤最为关键!!不要打开数据库。首先关闭数据库,然后把C点的控制文件恢复到在线控制文件的位置,然后用C点的控制文件恢复步骤(16)结束之后的数据文件,恢复进程会自动应用时刻B和时刻C之间的归档日志文件,从序列号为1的归档日志arch1.arc开始。注意:本例执行的是完全媒体恢复,必须在不丢失联机重做日志文件的情况下。否则,要恢复联机重做日志文件。当然,也可执行不完全媒体恢复,恢复到时刻B和时刻C之间的任一时刻。本步骤的关键技术在于要备份时刻C的控制文件,并用它实现跨越时刻B的媒体恢复。
SQL> shutdown
copy f:coolctl_cctl.ctl f: est1
copy f:coolctl_cctl.ctl f: est2
copy f:coolctl_cctl.ctl f: est3 SQL>
conn /@test as sysdba Connected to an idle instance.
SQL> startup mount
SQL> recover database;
ORA-00279: change 690773 generated at 10/04/2002 09:59:31 needed for thread 1
ORA-00289: suggestion : F:TESTARCH1.ARC
ORA-00280: change 690773 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
f:coolarchb_carch1.arc
ORA-00279: change 690989 generated at 10/04/2002 10:04:11 needed for thread 1
ORA-00289: suggestion : F:TESTARCH2.ARC
ORA-00280: change 690989 for thread 1 is in sequence #2
ORA-00278: log file 'f:coolarchb_carch1.arc' no longer needed for this
recovery
…… ……
Log applied.
Media recovery complete.
更多精彩
赞助商链接