Oracle数据库恢复教程之resetlogs操作

2020-07-26 13:58:31

字体：大中小

来源：转载

供稿：网友

实验环境：RHEL 5.4 + Oracle 11.2.0.3

如果是一名合格的Oracle DBA，对resetlogs这种关键字都应该是极其敏感的，当确认需要这种操作时一定要三思而后行，如果自己不是特别确认，哪怕多花些时间申请去让高级DBA人员协助你一起确认，也不要擅自去尝试执行，避免误操作造成既定损失后追悔莫及。

1.哪些场景可以resetlogs

首先要明确resetlogs操作非常危险的，也只有在进行不完全恢复开库时会使用到。

SQL> alter database open resetlogs;-> open the database and reset the online logs

官方的描述如下：

Incomplete recovery, also called database point-in-time recovery, results in a noncurrent version of the database. In this case, you do not apply all of the redo generated after the restored backup. Typically, you perform point-in-time database recovery to undo a user error when Flashback Database is not possible.
To perform incomplete recovery, you must restore all data files from backups created before the time to which you want to recover and then open the database with the RESETLOGS option when recovery completes. Resetting the logs creates a new stream of log sequence numbers starting with log sequence 1.

官方的描述其实很清晰，但是实际很多初级DBA小伙伴们在实际工作中遇到这样的场景时却总是有些困惑，甚至误操作引发灾难。

我这里以一个实验来具体说明常见场景：

需求：A机数据库PROD1，现需在B机不同目录下用A机的备份集恢复出来；

A机：

--A机当前current redolog的sequence是57:SQL> select * from v$log; GROUP# THREAD# SEQUENCE#  BYTES BLOCKSIZE MEMBERS ARC STATUS   FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME---------- ---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- --------- ------------ ---------   1   1   55 52428800  512   1 YES INACTIVE    2051572 19-MAY-19  2060361 19-MAY-19   2   1   56 52428800  512   1 YES INACTIVE    2060361 19-MAY-19  2060436 19-MAY-19   3   1   57 52428800  512   1 NO CURRENT    2060436 19-MAY-19 2.8147E+14--A机做了一次数据库备份：RMAN> backup database include current controlfile plus archivelog delete all input;Starting backup at 19-MAY-19current log archivedallocated channel: ORA_DISK_1channel ORA_DISK_1: SID=23 device type=DISKallocated channel: ORA_DISK_2channel ORA_DISK_2: SID=189 device type=DISKallocated channel: ORA_DISK_3channel ORA_DISK_3: SID=21 device type=DISKchannel ORA_DISK_1: starting compressed archived log backup setchannel ORA_DISK_1: specifying archived log(s) in backup setinput archived log thread=1 sequence=57 RECID=3 STAMP=1008670991channel ORA_DISK_1: starting piece 1 at 19-MAY-19channel ORA_DISK_1: finished piece 1 at 19-MAY-19piece handle=/home/oracle/backup/0cu1u68l_1_1.bak tag=TAG20190519T102315 comment=NONEchannel ORA_DISK_1: backup set complete, elapsed time: 00:00:01channel ORA_DISK_1: deleting archived log(s)archived log file name=/u01/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_57_860888149.dbf RECID=3 STAMP=1008670991Finished backup at 19-MAY-19Starting backup at 19-MAY-19using channel ORA_DISK_1using channel ORA_DISK_2using channel ORA_DISK_3channel ORA_DISK_1: starting compressed full datafile backup setchannel ORA_DISK_1: specifying datafile(s) in backup setinput datafile file number=00002 name=/u01/app/oracle/oradata/PROD1/sysaux01.dbfchannel ORA_DISK_1: starting piece 1 at 19-MAY-19channel ORA_DISK_2: starting compressed full datafile backup setchannel ORA_DISK_2: specifying datafile(s) in backup setinput datafile file number=00001 name=/u01/app/oracle/oradata/PROD1/system01.dbfinput datafile file number=00004 name=/u01/app/oracle/oradata/PROD1/users01.dbfchannel ORA_DISK_2: starting piece 1 at 19-MAY-19channel ORA_DISK_3: starting compressed full datafile backup setchannel ORA_DISK_3: specifying datafile(s) in backup setinput datafile file number=00005 name=/u01/app/oracle/oradata/PROD1/example01.dbfinput datafile file number=00003 name=/u01/app/oracle/oradata/PROD1/undotbs01.dbfchannel ORA_DISK_3: starting piece 1 at 19-MAY-19channel ORA_DISK_3: finished piece 1 at 19-MAY-19piece handle=/home/oracle/backup/0fu1u68p_1_1.bak tag=TAG20190519T102319 comment=NONEchannel ORA_DISK_3: backup set complete, elapsed time: 00:00:26channel ORA_DISK_3: starting compressed full datafile backup setchannel ORA_DISK_3: specifying datafile(s) in backup setincluding current control file in backup setchannel ORA_DISK_3: starting piece 1 at 19-MAY-19channel ORA_DISK_3: finished piece 1 at 19-MAY-19piece handle=/home/oracle/backup/0gu1u69j_1_1.bak tag=TAG20190519T102319 comment=NONEchannel ORA_DISK_3: backup set complete, elapsed time: 00:00:01channel ORA_DISK_1: finished piece 1 at 19-MAY-19piece handle=/home/oracle/backup/0du1u68p_1_1.bak tag=TAG20190519T102319 comment=NONEchannel ORA_DISK_1: backup set complete, elapsed time: 00:01:03channel ORA_DISK_2: finished piece 1 at 19-MAY-19piece handle=/home/oracle/backup/0eu1u68p_1_1.bak tag=TAG20190519T102319 comment=NONEchannel ORA_DISK_2: backup set complete, elapsed time: 00:01:23Finished backup at 19-MAY-19Starting backup at 19-MAY-19current log archivedusing channel ORA_DISK_1using channel ORA_DISK_2using channel ORA_DISK_3channel ORA_DISK_1: starting compressed archived log backup setchannel ORA_DISK_1: specifying archived log(s) in backup setinput archived log thread=1 sequence=58 RECID=4 STAMP=1008671084channel ORA_DISK_1: starting piece 1 at 19-MAY-19channel ORA_DISK_1: finished piece 1 at 19-MAY-19piece handle=/home/oracle/backup/0hu1u6bg_1_1.bak tag=TAG20190519T102446 comment=NONEchannel ORA_DISK_1: backup set complete, elapsed time: 00:00:01channel ORA_DISK_1: deleting archived log(s)archived log file name=/u01/app/oracle/product/11.2.0/dbhome_1/dbs/arch1_58_860888149.dbf RECID=4 STAMP=1008671084Finished backup at 19-MAY-19Starting Control File and SPFILE Autobackup at 19-MAY-19piece handle=/home/oracle/backup/control/c-2082231315-20190519-01 comment=NONEFinished Control File and SPFILE Autobackup at 19-MAY-19RMAN> --可以看到备份数据库的日志前后都自动归档了当前的redolog（57和58），所以备份完成后，当前日志sequence变为59.SQL> select * from v$log; GROUP# THREAD# SEQUENCE#  BYTES BLOCKSIZE MEMBERS ARC STATUS   FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME---------- ---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- --------- ------------ ---------   1   1   58 52428800  512   1 YES INACTIVE    2060691 19-MAY-19  2060767 19-MAY-19   2   1   59 52428800  512   1 NO CURRENT    2060767 19-MAY-19 2.8147E+14   3   1   57 52428800  512   1 YES INACTIVE    2060436 19-MAY-19  2060691 19-MAY-19

此时把备份集传输到B机，比如/u03/backup目录下，期望恢复到/u03/oradata/PROD1目录下。如果最终只是根据这个备份集去恢复，那最多恢复完sequence 58就结束了，找不到sequence 59（因为59还是当前current的redolog）。Oracle认为这就是最基本的不完全恢复，需要resetlogs操作。

--指定恢复到/u03/oradata/RMAN> run {2> set newname for database to '/u03/oradata/PROD1/%U';3> restore database;4> }--切换到上步恢复出来的copy复本：RMAN> switch database to copy;datafile 1 switched to datafile copy "/u03/oradata/PROD1/data_D-PROD1_TS-SYSTEM_FNO-1"datafile 2 switched to datafile copy "/u03/oradata/PROD1/data_D-PROD1_TS-SYSAUX_FNO-2"datafile 3 switched to datafile copy "/u03/oradata/PROD1/data_D-PROD1_TS-UNDOTBS1_FNO-3"datafile 4 switched to datafile copy "/u03/oradata/PROD1/data_D-PROD1_TS-USERS_FNO-4"datafile 5 switched to datafile copy "/u03/oradata/PROD1/data_D-PROD1_TS-EXAMPLE_FNO-5"--尝试恢复数据库：RMAN> recover database;Starting recover at 19-MAY-19using target database control file instead of recovery catalogallocated channel: ORA_DISK_1channel ORA_DISK_1: SID=102 device type=DISKallocated channel: ORA_DISK_2channel ORA_DISK_2: SID=9 device type=DISKallocated channel: ORA_DISK_3channel ORA_DISK_3: SID=112 device type=DISKstarting media recoverychannel ORA_DISK_1: starting archived log restore to default destinationchannel ORA_DISK_1: restoring archived logarchived log thread=1 sequence=58channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0hu1u6bg_1_1.bakchannel ORA_DISK_1: errors found reading piece handle=/home/oracle/backup/0hu1u6bg_1_1.bakchannel ORA_DISK_1: failover to piece handle=/u03/backup/0hu1u6bg_1_1.bak tag=TAG20190519T102446channel ORA_DISK_1: restored backup piece 1channel ORA_DISK_1: restore complete, elapsed time: 00:00:01archived log file name=/u01/app/oracle/product/11.2.0/db_1/dbs/arch1_58_860888149.dbf thread=1 sequence=58unable to find archived logarchived log thread=1 sequence=59RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of recover command at 05/19/2019 11:04:21RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 59 and starting SCN of 2060767RMAN>

可以看到最后有报错信息，就是告诉你找不到sequence 59的日志，这是必然的，因为59还是A机current的redo日志。

2.resetlogs前必须确认路径正确

2.1 先查看控制文件和数据文件头记录的scn是否一致

SQL> select checkpoint_change# from v$datafile;CHECKPOINT_CHANGE#------------------   2060767   2060767   2060767   2060767   2060767SQL> select checkpoint_change# from v$datafile_header;CHECKPOINT_CHANGE#------------------   2060767   2060767   2060767   2060767   2060767

2.2 此时如果尝试直接OPEN会报错

SQL> alter database open;alter database open*ERROR at line 1:ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

提示我们开库必须使用RESETLOGS或者NORESETLOGS选项。

2.3 重点来了，现在可以open resetlogs吗？

当然不行！记得一定要确认好路径！！

--查询发现临时文件以及redo日志的路径都不是我们所期望的：SQL> select name from v$datafile;NAME--------------------------------------------------------------------------------/u03/oradata/PROD1/data_D-PROD1_TS-SYSTEM_FNO-1/u03/oradata/PROD1/data_D-PROD1_TS-SYSAUX_FNO-2/u03/oradata/PROD1/data_D-PROD1_TS-UNDOTBS1_FNO-3/u03/oradata/PROD1/data_D-PROD1_TS-USERS_FNO-4/u03/oradata/PROD1/data_D-PROD1_TS-EXAMPLE_FNO-5SQL> select name from v$tempfile;NAME--------------------------------------------------------------------------------/u01/app/oracle/oradata/PROD1/temp01.dbfSQL> select member from v$logfile;MEMBER--------------------------------------------------------------------------------/u01/app/oracle/oradata/PROD1/redo03.log/u01/app/oracle/oradata/PROD1/redo02.log/u01/app/oracle/oradata/PROD1/redo01.log--rename重命名为我们期望的目录：SQL> alter database rename file '/u01/app/oracle/oradata/PROD1/temp01.dbf' to '/u03/oradata/PROD1/temp01.dbf';Database altered.SQL> alter database rename file '/u01/app/oracle/oradata/PROD1/redo01.log' to '/u03/oradata/PROD1/redo01.log';Database altered.SQL> alter database rename file '/u01/app/oracle/oradata/PROD1/redo02.log' to '/u03/oradata/PROD1/redo02.log';Database altered.SQL> alter database rename file '/u01/app/oracle/oradata/PROD1/redo03.log' to '/u03/oradata/PROD1/redo03.log';Database altered.--再次检查确认：SQL> select name from v$tempfile;NAME--------------------------------------------------------------------------------/u03/oradata/PROD1/temp01.dbfSQL> select member from v$logfile;MEMBER--------------------------------------------------------------------------------/u03/oradata/PROD1/redo03.log/u03/oradata/PROD1/redo02.log/u03/oradata/PROD1/redo01.log--最终尝试open开库：SQL> alter database open;alter database open*ERROR at line 1:ORA-01589: must use RESETLOGS or NORESETLOGS option for database openSQL> alter database open resetlogs;Database altered.

总结：

很多初级人员有可能是对set newname for database这个有误解，以为这里的database包括了临时文件，redo日志文件，误以为自己已经把新库所有路径都指向到了期望位置。但实际并不是这样，这也说明了不确认的操作一定要在测试环境测试验证后才可以在生产环境操作。大家可以想象一下，如果是理解有误没确认日志路径直接执行了resetlogs，那么如果B机正好有别的库用到同名的这些路径，亦或是整个恢复操作就是直接在A机的本机其他目录临时基于某个时间点恢复出一套库，那将会是一场大的生产事故。

好了，以上就是这篇文章的全部内容了，希望本文的内容对大家的学习或者工作具有一定的参考学习价值，谢谢大家对武林网的支持。

上一篇：关于Oracle Dataguard 日志传输状态监控问题

下一篇：Oracle 实现一个关键字匹配多个字段的方法