实验环境：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-19

current log archived

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=23 device type=DISK

allocated channel: ORA_DISK_2

channel ORA_DISK_2: SID=189 device type=DISK

allocated channel: ORA_DISK_3

channel ORA_DISK_3: SID=21 device type=DISK

channel ORA_DISK_1: starting compressed archived log backup set

channel ORA_DISK_1: specifying archived log(s) in backup set

input archived log thread=1 sequence=57 RECID=3 STAMP=1008670991

channel ORA_DISK_1: starting piece 1 at 19-MAY-19

channel ORA_DISK_1: finished piece 1 at 19-MAY-19

piece handle=/home/oracle/backup/0cu1u68l_1_1.bak tag=TAG20190519T102315 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

channel 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=1008670991

Finished backup at 19-MAY-19

Starting backup at 19-MAY-19

using channel ORA_DISK_1

using channel ORA_DISK_2

using channel ORA_DISK_3

channel ORA_DISK_1: starting compressed full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

input datafile file number=00002 name=/u01/app/oracle/oradata/PROD1/sysaux01.dbf

channel ORA_DISK_1: starting piece 1 at 19-MAY-19

channel ORA_DISK_2: starting compressed full datafile backup set

channel ORA_DISK_2: specifying datafile(s) in backup set

input datafile file number=00001 name=/u01/app/oracle/oradata/PROD1/system01.dbf

input datafile file number=00004 name=/u01/app/oracle/oradata/PROD1/users01.dbf

channel ORA_DISK_2: starting piece 1 at 19-MAY-19

channel ORA_DISK_3: starting compressed full datafile backup set

channel ORA_DISK_3: specifying datafile(s) in backup set

input datafile file number=00005 name=/u01/app/oracle/oradata/PROD1/example01.dbf

input datafile file number=00003 name=/u01/app/oracle/oradata/PROD1/undotbs01.dbf

channel ORA_DISK_3: starting piece 1 at 19-MAY-19

channel ORA_DISK_3: finished piece 1 at 19-MAY-19

piece handle=/home/oracle/backup/0fu1u68p_1_1.bak tag=TAG20190519T102319 comment=NONE

channel ORA_DISK_3: backup set complete, elapsed time: 00:00:26

channel ORA_DISK_3: starting compressed full datafile backup set

channel ORA_DISK_3: specifying datafile(s) in backup set

including current control file in backup set

channel ORA_DISK_3: starting piece 1 at 19-MAY-19

channel ORA_DISK_3: finished piece 1 at 19-MAY-19

piece handle=/home/oracle/backup/0gu1u69j_1_1.bak tag=TAG20190519T102319 comment=NONE

channel ORA_DISK_3: backup set complete, elapsed time: 00:00:01

channel ORA_DISK_1: finished piece 1 at 19-MAY-19

piece handle=/home/oracle/backup/0du1u68p_1_1.bak tag=TAG20190519T102319 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:01:03

channel ORA_DISK_2: finished piece 1 at 19-MAY-19

piece handle=/home/oracle/backup/0eu1u68p_1_1.bak tag=TAG20190519T102319 comment=NONE

channel ORA_DISK_2: backup set complete, elapsed time: 00:01:23

Finished backup at 19-MAY-19

Starting backup at 19-MAY-19

current log archived

using channel ORA_DISK_1

using channel ORA_DISK_2

using channel ORA_DISK_3

channel ORA_DISK_1: starting compressed archived log backup set

channel ORA_DISK_1: specifying archived log(s) in backup set

input archived log thread=1 sequence=58 RECID=4 STAMP=1008671084

channel ORA_DISK_1: starting piece 1 at 19-MAY-19

channel ORA_DISK_1: finished piece 1 at 19-MAY-19

piece handle=/home/oracle/backup/0hu1u6bg_1_1.bak tag=TAG20190519T102446 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

channel 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=1008671084

Finished backup at 19-MAY-19

Starting Control File and SPFILE Autobackup at 19-MAY-19

piece handle=/home/oracle/backup/control/c-2082231315-20190519-01 comment=NONE

Finished Control File and SPFILE Autobackup at 19-MAY-19

RMAN> 

--可以看到备份数据库的日志前后都自动归档了当前的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-19

using target database control file instead of recovery catalog

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=102 device type=DISK

allocated channel: ORA_DISK_2

channel ORA_DISK_2: SID=9 device type=DISK

allocated channel: ORA_DISK_3

channel ORA_DISK_3: SID=112 device type=DISK

starting media recovery

channel ORA_DISK_1: starting archived log restore to default destination

channel ORA_DISK_1: restoring archived log

archived log thread=1 sequence=58

channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0hu1u6bg_1_1.bak

channel ORA_DISK_1: errors found reading piece handle=/home/oracle/backup/0hu1u6bg_1_1.bak

channel ORA_DISK_1: failover to piece handle=/u03/backup/0hu1u6bg_1_1.bak tag=TAG20190519T102446

channel ORA_DISK_1: restored backup piece 1

channel ORA_DISK_1: restore complete, elapsed time: 00:00:01

archived log file name=/u01/app/oracle/product/11.2.0/db_1/dbs/arch1_58_860888149.dbf thread=1 sequence=58

unable to find archived log

archived log thread=1 sequence=59

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of recover command at 05/19/2019 11:04:21

RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 59 and starting SCN of 2060767

RMAN>

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

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

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

SQL> select checkpoint_change# from v$datafile;

CHECKPOINT_CHANGE#

------------------

           2060767

           2060767

           2060767

           2060767

           2060767

SQL> 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-5

SQL> select name from v$tempfile;

NAME

--------------------------------------------------------------------------------

/u01/app/oracle/oradata/PROD1/temp01.dbf

SQL> 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.dbf

SQL>  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 open

SQL> alter database open resetlogs;

Database altered.

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

Oracle数据库恢复之resetlogs的更多相关文章

Oracle 【IT实验室】数据库备份与恢复之：如何对Oracle数据库文件进行恢复与备份
任何数据库在长期使用过程中,都会存在一定的安全隐患.对于数据库管理员来说不能仅寄希望于计算机操作系统的安全运行,而是要建立一整套的数据库备份与恢复机制.当数据库发生故障后,希望能重新建立一个完整的数据 ...
Oracle备份恢复之rman备份oracle数据库
备份需求和rman备份 oracle数据库的备份相关问答: 1)备份时数据库处于何种状态? 备份时数据库处于OPEN状态,这样数据库可以正常工作. 2)备份的数据备份在什么地方? 备份在本地磁盘. 3 ...
RMAN数据库恢复之对数据库进行完全介质恢复
RMAN数据库恢复之对数据库进行完全介质恢复环境:控制文件和参数文件SPFILE及归档文件.重做日志文件都在.其它数据文件丢失.恢复方法:使用之前创建的全库备份进行恢复1.删除数据文件: SQL> ...
[转帖]oracle备份恢复之recover database的四条语句区别
oracle备份恢复之recover database的四条语句区别 https://www.cnblogs.com/andy6/p/5925433.html 需要学习一下. 1 recover d ...
Oracle数据库升级(10.2.0.4->11.2.0.4)
环境: RHEL5.4 + Oracle 10.2.0.4 目的: 在本机将数据库升级到11.2.0.4 之前总结的Oracle数据库异机升级:http://www.cnblogs.com/jyzha ...
Oracle数据库基础知识
oracle数据库plsql developer 目录(?)[-] 一 SQL基础知识创建删除数据库创建删除修改表添加修改删除列 oracle cascade用法添加删除约束主键外 ...
oracle数据库相关知识点
已知表如下:
【转】oracle数据库开发的一些经验积累
1.不安装Oracle客户连接Oracle 8的方法请将以下文件拷贝到运行文件所在目录一.ODBC动态库 : ctl3d32.dll msvcrt40.dll odbc16gt.dll odbc ...
服务器断电,Oracle数据库无法启动解决方案
数据库没有备份的情况下,数据库所在服务器由于意外断电,导致服务器启动之后,Oracle数据库startup报错. 1. 数据库没开归档模式 2. 无备份解决方案: 1 2 3 4 5 6 7 8 9 ...

随机推荐

dom 显示与否的对 ecmascript 变量的监听
dom 显示与否的对 ecmascript 变量的监听
EF学习和使用（三）Code First
Code First模式我们称之为"代码优先"模式.从某种角度来看.其实"Code First"和"Model First"区别并非太明显. ...
【AWS】亚马逊云常用服务解释
新公司使用的是亚马逊服务,刚开始的时候,对很多名词不太明白,总结了一下如下 1,EC2 这个是亚马逊的一种服务器服务,可以理解为跟vmware差不多,EC2为虚拟机提供载体,EC2上跑虚拟机服务器. ...
python连接redis并插入url
#!/usr/bin/env python # -*- coding:utf8 -*- import redis ''' 这种连接是连接一次就断了,耗资源.端口默认6379,就不用写 r = redi ...
java多线程---基础
一, java多线程----线程与进程进程: 程序(任务)的执行过程,拥有资源(共享内存,共享资源)和线程(一个或者多个,至少一个). 例如:打开任务管理器,qq,chrome,都属于进程. 线程 ...
数据解析,懒加载,代理ip
在前面的requests流程中,还缺少了一步重要的流程,就是在持久化存储之前需要进行制定的数据解析.因为在大多数情况下,我们都会使用聚焦爬虫,也就是爬取页面中的指定部分数据值,而不是整个页面的数据. ...
quick check
SQL Server 2008R2 代理服务-开启
,点击开始菜单-所有程序-SQLServer2008R2-配置工具-SQLServer配置管理器 2,选择SQLServer服务 3,找到SqlServer代理(MSSQLSERVER),双击或右键选 ...
matlab之text()函数
text()函数用来给图加上说明性文字. 格式:text(x,y,'txt') 或者:text(x,y,'txt','color','k') x,y是位置 txt是说明文字,如果说明性文字是数字,则这 ...
javascript(6)
javascript的冒泡排序 var arr=[5,0,-56,900,12]; //大的排序次数(arr.length-1) var flag=false; for(var i=0;i<=a ...

Oracle数据库恢复之resetlogs

1.哪些场景可以resetlogs

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

Oracle数据库恢复之resetlogs的更多相关文章

随机推荐

热门专题