rman基于SCN的不完全恢复
2017-06-15 15:41
363 查看
本文描述:通过日志挖掘来恢复被删对象的过程
试验过程:
注:试验前先将数据库全备或者0级备份
全备:backup database format 'g:\rmanbak\db_%d_%T_%s.bak'
plus archivelog format 'g:\rmanbak\arch_%d_%T_%s.bak';
0级备份:backup incremental level 0 database format 'g:\rmanbak\db_%d_%T_%s.bak'
plus archivelog format 'g:\rmanbak\arch_%d_%T_%s.bak';
(1)删除Scott用户的表emp,并创建表t2
(2)通过日志挖掘找到删除表emp的SCN,取SCN=SCN-1为未删除表emp时的数据库状态
(3)登录rman进行恢复
(4)登录Scott,查询恢复结果
试验过程:
注:试验前先将数据库全备或者0级备份
全备:backup database format 'g:\rmanbak\db_%d_%T_%s.bak'
plus archivelog format 'g:\rmanbak\arch_%d_%T_%s.bak';
0级备份:backup incremental level 0 database format 'g:\rmanbak\db_%d_%T_%s.bak'
plus archivelog format 'g:\rmanbak\arch_%d_%T_%s.bak';
(1)删除Scott用户的表emp,并创建表t2
C:\Users\Administrator>sqlplus / as sysdba SQL*Plus: Release 11.2.0.1.0 Production on 星期三 6月 14 15:30:29 2017 Copyright (c) 1982, 2010, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> conn scott/tiger Connected. SQL> select * from tab; TNAME TABTYPE CLUSTERID ------------------------------ ------- ---------- BONUS TABLE DEPT TABLE EMP TABLE SALGRADE TABLE SQL> drop table emp purge; Table dropped. SQL> create table t2 tablespace tt as select * from dept; Table created. SQL> select * from tab; TNAME TABTYPE CLUSTERID ------------------------------ ------- ---------- BONUS TABLE DEPT TABLE SALGRADE TABLE T2 TABLE
(2)通过日志挖掘找到删除表emp的SCN,取SCN=SCN-1为未删除表emp时的数据库状态
SQL> conn / as sysdba Connected. SQL> select 'exec dbms_logmnr.add_logfile('''||member||''')' from v$logfile; 'EXECDBMS_LOGMNR.ADD_LOGFILE('''||MEMBER||''')' -------------------------------------------------------------------------------- exec dbms_logmnr.add_logfile('F:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG') exec dbms_logmnr.add_logfile('F:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO02.LOG') exec dbms_logmnr.add_logfile('F:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO01.LOG') SQL> exec dbms_logmnr.add_logfile('F:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG'); PL/SQL procedure successfully completed. SQL> exec dbms_logmnr.add_logfile('F:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO02.LOG'); PL/SQL procedure successfully completed. SQL> exec dbms_logmnr.add_logfile('F:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO01.LOG'); PL/SQL procedure successfully completed. SQL> exec dbms_logmnr.start_logmnr(); PL/SQL procedure successfully completed. SQL> select scn,sql_redo from v$logmnr_contents 2 where seg_name='EMP' 3 and seg_owner='SCOTT' 4 and sql_redo like '%drop table emp%'; no rows selected SQL> exec dbms_logmnr.add_logfile('F:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO03.LOG'); PL/SQL procedure successfully completed. SQL> exec dbms_logmnr.add_logfile('F:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO02.LOG'); PL/SQL procedure successfully completed. SQL> exec dbms_logmnr.add_logfile('F:\APP\ADMINISTRATOR\ORADATA\ORCL\REDO01.LOG'); PL/SQL procedure successfully completed. SQL> exec dbms_logmnr.start_logmnr(); PL/SQL procedure successfully completed. SQL> select scn,sql_redo from v$logmnr_contents 2 where seg_name='EMP' 3 and seg_owner='SCOTT' 4 and sql_redo like '%drop table emp%'; SCN SQL_REDO --------------- --------------------------------- 1378007 drop table emp purge; SQL>
(3)登录rman进行恢复
C:\Users\Administrator>rman target / Recovery Manager: Release 11.2.0.1.0 - Production on 星期三 6月 14 15:11:55 2017 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. connected to target database: ORCL (DBID=1468451227) RMAN> run{ 2> shutdown immediate 3> startup mount 4> set until scn=1378007; 5> restore database; 6> recover database; 7> sql 'alter database open resetlogs'; 8> } database closed database dismounted Oracle instance shut down connected to target database (not started) Oracle instance started database mounted Total System Global Area 430075904 bytes Fixed Size 2176448 bytes Variable Size 322964032 bytes Database Buffers 96468992 bytes Redo Buffers 8466432 bytes executing command: SET until clause Starting restore at 14-6月 -17 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=63 device type=DISK creating datafile file number=12 name=F:\ORADATA\TT01.DBF channel ORA_DISK_1: starting datafile backup set restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set channel ORA_DISK_1: restoring datafile 00001 to F:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01.DBF channel ORA_DISK_1: restoring datafile 00002 to F:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSAUX01.DBF channel ORA_DISK_1: restoring datafile 00003 to F:\APP\ADMINISTRATOR\ORADATA\ORCL\UNDOTBS01.DBF channel ORA_DISK_1: restoring datafile 00004 to F:\APP\ADMINISTRATOR\ORADATA\ORCL\USERS01.DBF channel ORA_DISK_1: restoring datafile 00005 to F:\APP\ADMINISTRATOR\ORADATA\ORCL\EXAMPLE01.DBF channel ORA_DISK_1: restoring datafile 00006 to F:\ORADATA\BASE_DATA01.DBF channel ORA_DISK_1: restoring datafile 00007 to F:\ORADATA\BASE_INDEX01.DBF channel ORA_DISK_1: restoring datafile 00008 to F:\ORADATA\MATCH_DATA01.DBF channel ORA_DISK_1: restoring datafile 00009 to F:\ORADATA\MATCH_INDEX01.DBF channel ORA_DISK_1: restoring datafile 00010 to F:\ORADATA\MATCHDETAIL_DATA01.DBF channel ORA_DISK_1: restoring datafile 00011 to F:\ORADATA\MATCHDETAIL_INDEX01.DBF channel ORA_DISK_1: reading from backup piece G:\RMANBP\FDB_ORCL_20170613_14.BAK channel ORA_DISK_1: piece handle=G:\RMANBP\FDB_ORCL_20170613_14.BAK tag=TAG20170613T123834 channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:04:36 Finished restore at 14-6月 -17 Starting recover at 14-6月 -17 using channel ORA_DISK_1 starting media recovery archived log for thread 1 with sequence 74 is already on disk as file F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_13\O1_MF_1_74_D MYVCR6Q_.ARC archived log for thread 1 with sequence 75 is already on disk as file F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_13\O1_MF_1_75_D MYVTGMD_.ARC archived log for thread 1 with sequence 76 is already on disk as file F:\APP\ADMINISTRATOR 4000 \FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_13\O1_MF_1_76_D MZ8PWJ1_.ARC archived log for thread 1 with sequence 77 is already on disk as file F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_14\O1_MF_1_77_D N155JPS_.ARC archived log for thread 1 with sequence 78 is already on disk as file F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_14\O1_MF_1_78_D N16YS6W_.ARC archived log for thread 1 with sequence 79 is already on disk as file F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_14\O1_MF_1_79_D N17JN2C_.ARC archived log for thread 1 with sequence 80 is already on disk as file F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_14\O1_MF_1_80_D N17RDDN_.ARC archived log for thread 1 with sequence 81 is already on disk as file F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_14\O1_MF_1_81_D N1FMP5Z_.ARC archived log for thread 1 with sequence 82 is already on disk as file F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_14\O1_MF_1_82_D N1HKJSX_.ARC archived log for thread 1 with sequence 83 is already on disk as file F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_14\O1_MF_1_83_D N1Q41L1_.ARC archived log file name=F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_13\O1_MF_1_74_DMYVCR6Q_.ARC thread=1 sequence=74 archived log file name=F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_13\O1_MF_1_75_DMYVTGMD_.ARC thread=1 sequence=75 archived log file name=F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_13\O1_MF_1_76_DMZ8PWJ1_.ARC thread=1 sequence=76 archived log file name=F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_14\O1_MF_1_77_DN155JPS_.ARC thread=1 sequence=77 archived log file name=F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_14\O1_MF_1_78_DN16YS6W_.ARC thread=1 sequence=78 archived log file name=F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_14\O1_MF_1_79_DN17JN2C_.ARC thread=1 sequence=79 archived log file name=F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_14\O1_MF_1_80_DN17RDDN_.ARC thread=1 sequence=80 archived log file name=F:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2017_06_14\O1_MF_1_81_DN1FMP5Z_.ARC thread=1 sequence=81 media recovery complete, elapsed time: 00:00:23 Finished recover at 14-6月 -17 sql statement: alter database open resetlogs RMAN>
(4)登录Scott,查询恢复结果
SQL> conn scott/tiger Connected. SQL> select * from tab; TNAME TABTYPE CLUSTERID ------------------------------ ------- ---------- BONUS TABLE DEPT TABLE EMP TABLE SALGRADE TABLE SQL>恢复成功!
相关文章推荐
- 使用RMAN的不完全恢复-基于时间/SCN/日志序列
- RMAN基于SCN或特定时间点的不完全恢复
- 使用RMAN的不完全恢复-基于时间/SCN/日志序列
- Oracle 基于 RMAN 的不完全恢复(incomplete recovery by RMAN)
- RMAN—实验—基于SCN的恢复
- ARCHIVELOG模式下用户管理的不完全恢复(2)——基于SCN的不完全恢复!
- RMAN基于表空间的不完全恢复(TSPITR)
- 恢复到特定点(时间点、scn、日志序列号),rman不完全恢复
- 基于时间不完全恢复之rman篇
- Oracle 基于 RMAN 的不完全恢复(incomplete recovery by RMAN)
- rman基于备份的控制文件的不完全恢复
- RMAN备份与恢复—基于日志序列号的不完全恢复
- RMAN基于时间点的不完全恢复
- rman 基于时间的不完全恢复
- Orace入门之RMAN基于时间点的不完全恢复
- Oracle 基于 RMAN 的不完全恢复(incomplete recovery by RMAN)
- DDL误操作基于scn的不完全恢复
- RMAN基于表空间的不完全恢复(TSPITR)
- RMAN备份与恢复之基于时间点的不完全恢复
- 第6天-3 RMAN不完全恢复】【用scn恢复到特定的时刻】【控制文件损坏】【损坏日志文件状态非INACTIVE时,数据库打不开】【增加联机日志文件】【修改所有联机日志大小同义10M】