HowTo Restore RMAN Disk backups of RAC Database to Single Instance On Another Node (Doc ID 415579.1)

APPLIES TO:

Oracle Database - Enterprise Edition - Version 9.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 15-Apr-2014***

GOAL

- You have a RAC database backed up by RMAN to disk location  您有一个由RMAN备份到磁盘位置的RAC数据库
- You need to restore this backup as Single Instance on another node  您需要将此备份还原为另一个节点上的单实例

SOLUTION

1) Take appropriate RMAN backup of the production RAC database. Note that you should turn on the CONTROLFILE AUTOBACKUP configuration so that we have the controlfile backed up after the database backup. When we restore the controlfile on new host from this autobackup piece, it will have the information of the latest backup.

对生产RAC数据库进行适当的RMAN备份。请注意，您应该打开 CONTROLFILE AUTOBACKUP 配置，以便在数据库备份之后备份控制文件。当我们从此自动备份片段将控制文件还原到新主机上时，它将具有最新备份的信息。

  1. RMAN> run{
  2. 2> allocate channel c1 type disk format '/<PATH>/%U';
  3. 3> backup database;
  4. 4> backup archivelog all;
  5. 5> }
  6.  
  7. allocated channel: c1
  8. channel c1: sid=133 instance=<oracle_sid> devtype=DISK
  9.  
  10. Starting backup at 12-FEB-07
  11. channel c1: starting full datafile backupset
  12. channel c1: specifying datafile(s) in backupset
  13. input datafile fno=00001 name=/<PATH>/system01.dbf
  14. input datafile fno=00002 name=/<PATH>/undotbs01.dbf
  15. input datafile fno=00005 name=/<PATH>/undotbs02.dbf
  16. input datafile fno=00003 name=/<PATH>/sysaux01.dbf
  17. input datafile fno=00004 name=/<PATH>/users01.dbf
  18. channel c1: starting piece 1 at 12-FEB-07
  19. channel c1: finished piece 1 at 12-FEB-07
  20. piece handle=/<PATH>/09i9sruq_1_1 tag=TAG20070212T162458 comment=NONE
  21. channel c1: backup set complete, elapsed time: 00:01:05
  22. Finished backup at 12-FEB-07
  23.  
  24. Starting backup at 12-FEB-07
  25. current log archived
  26. channel c1: starting archive log backupset
  27. channel c1: specifying archive log(s) in backup set
  28. input archive log thread=1 sequence=56 recid=3 stamp=613417105
  29. input archive log thread=1 sequence=57 recid=4 stamp=613417106
  30. input archive log thread=1 sequence=58 recid=5 stamp=614363168
  31. input archive log thread=2 sequence=1 recid=1 stamp=613417090
  32. input archive log thread=2 sequence=2 recid=2 stamp=613417093
  33. input archive log thread=2 sequence=3 recid=6 stamp=614363170
  34. channel c1: starting piece 1 at 12-FEB-07
  35. channel c1: finished piece 1 at 12-FEB-07
  36. piece handle=/<PATH>/0ai9ss14_1_1 tag=TAG20070212T162610 comment=NONE
  37. channel c1: backup set complete, elapsed time: 00:00:04
  38. Finished backup at 12-FEB-07
  39.  
  40. Starting Control File and SPFILE Autobackup at 12-FEB-07
  41. piece handle=/<PATH>/c-610677177-20070212-00 comment=NONE
  42. Finished Control File and SPFILE Autobackup at 12-FEB-07
  43. released channel: c1

2) Create a PFILE for the single instance database using the production RAC parameter file  使用生产RAC参数文件为单实例数据库创建PFILE
a) don't forget to modify the following parameters depending on the directory structure of the new host: audit_file_dest, background_dump_dest, control_files, core_dump_dest, log_archive_dest_1, user_dump_dest etc  不要忘记根据新主机的目录结构修改以下参数：audit_file_dest, background_dump_dest, control_files, core_dump_dest, log_archive_dest_1, user_dump_dest 等
b) remove RAC specific parameters such as cluster_database_instances, cluster_database etc  删除RAC特定的参数，例如 cluster_database_instances，cluster_database 等
c) for the parameter undo_tablespace, mention any one undo tablespace name  对于参数undo_tablespace，使用任何一个undo表空间名称

Known issue which may require an additional parameter to be set :  --可能需要设置其他参数的已知问题
   Note 334899.1RMAN Duplicate from RAC backup fails ORA-38856

3) Move the backup pieces and the modified INIT.ORA file to the new host. Starting from 10g it is NO longer compulsory to copy the RMAN backup pieces to exactly the same location on the new host as the production location.
    将备份片段和修改后的INIT.ORA文件移动到新主机。从10g开始，不再必须将RMAN备份片段复制到新主机上与生产位置完全相同的位置。
4) Use the pfile created above to STARTUP NOMOUNT the database on the new host  使用上面创建的pfile在新主机上启动NOMOUNT数据库

  1. oracle@test-br ractest]$ sqlplus "/ as sysdba"
  2.  
  3. SQL*Plus: Release 10.2.0.1.0 - Production on Fri Feb 16 03:14:23 2007
  4.  
  5. Copyright (c) 1982, 2005, Oracle.  All rights reserved.
  6.  
  7. Connected to an idle instance.
  8.  
  9. SQL> startup nomount;
  10. ORACLE instance started.
  11.  
  12. Total System Global Area  167772160 bytes
  13. Fixed Size                  1218292 bytes
  14. Variable Size              62916876 bytes
  15. Database Buffers           96468992 bytes
  16. Redo Buffers                7168000 bytes

5) Now invoke RMAN and restore the controlfile specifying the location where the controlfile autobackup piece is restored on this new server. You can mount the database once the controlfile is restored successfully.

现在调用RMAN并还原控制文件，并指定该文件在该新服务器上的还原位置。控制文件成功还原后，您可以装载数据库

  1. [oracle@test-br ractest]$ rman target / nocatalog
  2.  
  3. Recovery Manager: Release 10.2.0.1.0 - Production on Fri Feb 16 03:16:31 2007
  4.  
  5. Copyright (c) 1982, 2005, Oracle.  All rights reserved.
  6.  
  7. connected to target database: <db_name> (not mounted)
  8. using target database control file instead of recovery catalog
  9.  
  10. RMAN> restore controlfile from '/<PATH>/c-610677177-20070212-00';
  11.  
  12. Starting restore at 16-FEB-07
  13. allocated channel: ORA_DISK_1
  14. channel ORA_DISK_1: sid=156 devtype=DISK
  15.  
  16. channel ORA_DISK_1: restoring control file
  17. channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
  18. output filename=/<PATH>/control01.ctl
  19. Finished restore at 16-FEB-07
  20.  
  21. RMAN> alter database mount;
  22.  
  23. database mounted
  24. released channel: ORA_DISK_1

6) You can skip this step if you have restored the RMAN backup pieces to exactly the same location they were backed up on production. If this is not the case then you need to catalog the RMAN backup pieces to make RMAN aware of their new location on the new host. Note that CATALOG BACKUPPIECE command is available only starting from 10g.

如果已将RMAN备份片段还原到生产中备份的完全相同的位置，则可以跳过此步骤。如果不是这种情况，则需要对RMAN备份块进行分类，以使RMAN知道它们在新主机上的新位置。注意，CATALOG BACKUPPIECE 命令仅从10g开始可用。

  1. RMAN> catalog backuppiece '/<PATH>/09i9sruq_1_1';
  2.  
  3. cataloged backuppiece
  4. backup piece handle=/<PATH>/09i9sruq_1_1 recid=10 stamp=614661579
  5.  
  6. RMAN> catalog backuppiece '/<PATH>/0ai9ss14_1_1';
  7.  
  8. cataloged backuppiece
  9. backup piece handle=/<PATH>/0ai9ss14_1_1 recid=11 stamp=614661599

7) Now we'll determine the point upto which media recovery should run on the restored database.

现在，我们确定在恢复的数据库上应该运行介质恢复的时间点

  1. RMAN> list backup of archivelog all;
  2.  
  3. List of Archived Logs in backup set 9
  4. Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  5. ---- ------- ---------- --------- ---------- ---------
  6. 1    56      214541     01-FEB-07 226238     01-FEB-07
  7. 1    57      226238     01-FEB-07 226240     01-FEB-07
  8. 1    58      226240     01-FEB-07 233107     12-FEB-07
  9. 2    1       186185     28-JAN-07 225714     01-FEB-07
  10. 2    2       225714     01-FEB-07 226037     01-FEB-07
  11. 2    3       226037     01-FEB-07 233110     12-FEB-07

Check the last archive sequence for all redo threads and select the archive sequence having LEAST "Next SCN" among them. In our case sequence 58 of thread 1 has Next SCN of 233107 while sequence 3 of thread 2 has Next SCN of 233110. Since squence 58 of thread 1 has least Next SCN we will recover upto this point. (If you are keen to have recovery run until some specific time you can always give SET UNTIL TIME)

检查所有 redo 线程的最后一个归档序列，并选择其中具有最低 "Next SCN" 的归档序列。在我们的情况下，线程1的序列58的Next SCN为233107，而线程2的序列3的Next SCN为233110。由于线程1的序列58的Next SCN最少，我们将恢复到这一点。（如果您希望在特定时间之前执行恢复，则可以始终设置 SET UNTIL TIME）

8) Having determined the point upto which media recovery should run, start the restore/recovery using:  确定应该运行介质恢复的时间点后，使用以下命令开始 restore/recovery

Please note in below example we choose Until sequence as 59(one more then the value selected in step  7 that is sequence 58)  because When we specify a sequence number, it is considered as an UPPER limit, RMAN selects only

请使用以下步骤开始恢复：请注意，在以下示例中，我们选择 Until sequence 为59（比在步骤7中选择的值（序列58多一个）），因为当我们指定序列号时，它被视为 UPPER limit ，RMAN仅选择

those  files which are needed for the recovery and uses 59 as an upper log sequence number while recovering database and would recovery upt log sequence number upto 58  .

恢复所需的文件，在恢复数据库时使用59作为较高的日志序列号，并且最多恢复58个日志序列号。

  1. RMAN> run {
  2. 2> set until sequence 59 thread 1;
  3. 3> set newname for datafile 1 to '/<PATH>/system01.dbf';
  4. 4> set newname for datafile 2 to '/<PATH>/undotbs01.dbf';
  5. 5> set newname for datafile 3 to '/<PATH>/sysaux01.dbf';
  6. 6> set newname for datafile 4 to '/<PATH>/users01.dbf';
  7. 7> set newname for datafile 5 to '/<PATH>/undotbs02.dbf';
  8. 8> restore database;
  9. 9> switch datafile all;
  10. 10> recover database;
  11. 11> }
 
In case you want to have the datafiles on a ASM diskgroup for the clone/destination database, you may use SET NEWNAME as below:
如果要将数据文件放在克隆/目标数据库的ASM磁盘组上，则可以使用SET NEWNAME，如下所示

  1. set newname for datafile 1 to '+<disk_group>';
  2. set newname for datafile 2 to '+<disk_group>';
  3. ....

Known issue in Oracle10g:
   Note 1146703.1 Rman Restore From RAC ASM To Single Instance Non ASM Fails With ORA-00600 [kgeade_is_0]

CAUTION !!!!:  小心!!!!

If Online Redolog's (ORL's) are Oracle Managed Files (OM), and the Clone is being done on any of Source RAC Node (where ORLs are accessible from), renaming ORL will try to remove Source ORL files!

如果 Online Redolog（ORL）是 Oracle Managed Files（OM），并且正在任何Source RAC Node（可从中访问ORL）上完成克隆，则重命名ORL将尝试删除Source ORL文件
Please review: http://docs.oracle.com/cd/E11882_01/server.112/e25494/omf.htm#ADMIN11517

The following statements are used to rename files: 以下语句用于重命名文件

  1. ALTER DATABASE RENAME FILE
  2. ALTER TABLESPACE ... RENAME DATAFILE

These statements do not actually rename the files on the operating system, but rather, the names in the control file are changed. If the old file is an Oracle managed file and it exists, then it is deleted. You must specify each filename using the conventions for filenames on your operating system when you issue this statement."

这些语句实际不重命名操作系统上的文件，而是更改控制文件中的名称。如果旧文件是Oracle managed file并且存在，则将其删除。发出此语句时，必须使用操作系统上文件名的conventions指定每个文件名
Instead of renaming, we can recreate the controlfile with desired name for ORLs:  除了重命名，我们还可以使用所需的ORL名称重新创建控制文件

  1. SQL> alter database backup controlfile to trace as '/tmp/control.sql' resetlogs ;
Edit /tmp/control.sql and modify desired ORL names.  编辑 /tmp/control.sql 并修改所需的ORL名称

Since we determined previously that media recovery should run until sequence 58 hence we use  SET UNTIL SEQUENCE 59 (+1) above. You also need to use SET NEWNAME clause to restore datafiles to a location on the new host which is different from the production path. Finally, SWITCH DATAFILE ALL clause updates these new datafile locations in the controlfile.

由于我们之前确定介质恢复应运行到序列58，因此我们使用上面的 SET UNTIL SEQUENCE 59（+1）。您还需要使用SET NEWNAME子句将数据文件还原到新主机上与生产路径不同的位置。最后，SWITCH DATAFILE ALL子句更新控制文件中的这些新数据文件位置。

9) Once RMAN restore/recovery finishes, you will want to rename the online redolog files before opening the database in case the production path of redo log files is not available on the new host. After renaming the redolog files, the database can be opened with RESETLOGS

RMAN restore/recovery 完成后，如果 online redolog files 的生产路径在新主机上不可用，您将需要在打开数据库之前重命名 online redolog files。重命名重做日志文件后，可以使用RESETLOGS打开数据库

  1. SQL> select member from v$logfile;
  2.  
  3. MEMBER
  4. --------------------------------------------------------------------------------
  5. /<old_path>/redo01.log
  6. /<old_path>/redo02.log
  7. /<old_path>/redo03.log
  8. /<old_path>/redo04.log
  9. /<old_path>/redo05.log
  10. /<old_path>/redo06.log
  11.  
  12. 6 rows selected.
  13.  
  14. SQL> alter database rename file '/<old_path>/redo01.log' to '/<new_path>/redo01.log';
  15.  
  16. Database altered.
  17.  
  18. SQL> alter database rename file '/<old_path>/redo02.log' to '/<new_path>/redo02.log';
  19.  
  20. Database altered.
  21.  
  22. SQL> alter database rename file '/<old_path>/redo03.log' to '/<new_path>/redo03.log';
  23.  
  24. Database altered.
  25.  
  26. SQL> alter database rename file '/<old_path>/redo04.log' to '/<new_path>/redo04.log';
  27.  
  28. Database altered.
  29.  
  30. SQL> alter database rename file '/<old_path>/redo05.log' to '/<new_path>/redo05.log';
  31.  
  32. Database altered.
  33.  
  34. SQL> alter database rename file '/<old_path>/redo06.log' to '/<new_path>/redo06.log';
  35.  
  36. Database altered.
  37.  
  38. SQL> alter database open resetlogs;
  39.  
  40. Database altered.
 
In case you want to create the online redo logs on a ASM diskgroup (+DATA for eg) for the clone/destination database, you may use below commands:
如果要在ASM磁盘组（例如+ DATA）上为克隆/目标数据库创建联机重做日志，则可以使用以下命令

  1. alter database rename file '/<old_path>/redo01.log' to '+<disk_group>';
  2. alter database rename file '/<old_path>/redo02.log' to '+<disk_group>';
  3. ...

10) Once the database is opened successfully, you may remove the redolog groups for redo threads of other instances

成功打开数据库后，您可以删除其他实例的重做线程的重做组

  1. SQL> select THREAD#, STATUS, ENABLED
  2.   2  from v$thread;
  3.  
  4.    THREAD# STATUS ENABLED
  5. ---------- ------ --------
  6.          1 OPEN   PUBLIC
  7.          2 CLOSED PRIVATE
  8.  
  9. SQL> select group# from v$log where THREAD#=2;
  10.  
  11.     GROUP#
  12. ----------
  13.          4
  14.          5
  15.          6
  16.  
  17. SQL> alter database disable thread 2;
  18.  
  19. Database altered.
  20.  
  21. SQL> alter database drop logfile group 4;
  22. alter database drop logfile group 4
  23. *
  24. ERROR at line 1:
  25. ORA-00350: log 4 of instance racdb2 (thread 2) needs to be archived
  26. ORA-00312: online log 4 thread 2: '/<PATH>/redo04.log'
  27.  
  28. SQL> alter database clear unarchived logfile group 4;
  29.  
  30. Database altered.
  31.  
  32. SQL> alter database drop logfile group 4;
  33.  
  34. Database altered.
  35.  
  36. SQL> alter database drop logfile group 5;
  37.  
  38. Database altered.
  39.  
  40. SQL> alter database drop logfile group 6;
  41.  
  42. Database altered.
  43.  
  44. SQL> select THREAD#, STATUS, ENABLED from v$thread;
  45.  
  46.    THREAD# STATUS ENABLED
  47. ---------- ------ --------
  48.          1 OPEN   PUBLIC　

11) Now you can remove the undo tablespaces of other instances and create a new temporary tablespace to complete the activity.

现在，您可以删除其他实例的UNDO表空间，并创建一个新的TEMP表空间以完成活动

  1. SQL> sho parameter undo;
  2.  
  3. NAME                                 TYPE        VALUE
  4. ------------------------------------ ----------- ------------------------------
  5. undo_management                      string      AUTO
  6. undo_retention                       integer     900
  7. undo_tablespace                      string      UNDOTBS1
  8. SQL>
  9. SQL>
  10. SQL> select tablespace_name from dba_tablespaces where contents='UNDO';
  11.  
  12. TABLESPACE_NAME
  13. ------------------------------
  14. UNDOTBS1
  15. UNDOTBS2
  16.  
  17. SQL> drop tablespace UNDOTBS2 including contents and datafiles;
  18.  
  19. Tablespace dropped.
  20.  
  21. SQL> select name from v$tempfile;
  22.  
  23. NAME
  24. --------------------------------------------------------------------------------
  25. /<PATH>/temp01.dbf
  26.  
  27. SQL> select tablespace_name from dba_tablespaces where contents='TEMPORARY';
  28.  
  29. TABLESPACE_NAME
  30. ------------------------------
  31. TEMP
  32.  
  33. SQL> create temporary tablespace TEMP1
  34.   2  tempfile '/<PATH>/temp01.dbf'
  35.   3  size 50M;
  36.  
  37. Tablespace created.
  38.  
  39. SQL> alter database default temporary tablespace TEMP1;
  40.  
  41. Database altered.
  42.  
  43. SQL> drop tablespace TEMP including contents and datafiles;
  44.  
  45. Tablespace dropped.

REFERENCES

NOTE:1146703.1 - Rman Restore From RAC ASM To Single Instance Non ASM Fails With ORA-00600 [kgeade_is_0]

如何将RAC数据库的 RMAN Disk 备份 Restore 到另一个节点上的单个实例 (Doc ID 415579.1)的更多相关文章

  1. How To Restore Rman Backups On A Different Node When The Directory Structures Are Different (Doc ID 419137.1)

    How To Restore Rman Backups On A Different Node When The Directory Structures Are Different (Doc ID ...

  2. RAC数据库的RMAN备份异机恢复到单节点数据库

    1.首先在rac环境用rman备份数据库.[oracle@rac1 admin]$ rman target /run{allocate channel c1 device type disk conn ...

  3. 在没有备份的情况下重新创建丢失的数据文件 (Doc ID 1149946.1)

    Recreating a missing datafile with no backups (Doc ID 1149946.1) APPLIES TO: Oracle Database - Enter ...

  4. 中小型数据库 RMAN CATALOG 备份恢复方案(一)

    对于数据库的稳定性,高可用,跨平台以及海量数据库的处理,Oracle 数据库通常是大型数据库和大企业的首选.尽管如此,仍然不乏很多中小企业想要品尝一下Oracle腥味,因此在Oracle环境中也有不少 ...

  5. Oracle RAC 实验环境RMAN备份v1.01

    Oracle RAC 实验环境RMAN备份v1.01 环境:RHEL 6.5 + Oracle GI 11.2.0.4 + RAC 11.2.0.4 (2 nodes) 需求:制定RAMN备份策略 版 ...

  6. 【RAC】将单实例备份集恢复为rac数据库

    [RAC]将单实例备份集恢复为rac数据库 一.1  BLOG文档结构图 一.2  前言部分 一.2.1  导读 各位技术爱好者,看完本文后,你可以掌握如下的技能,也可以学到一些其它你所不知道的知识, ...

  7. 中小型数据库 RMAN CATALOG 备份恢复方案(二)

    中小型数据库呈现的是数据库并发少,数据库容量小,版本功能受限以及N多单实例等特点.尽管如此,数据库的损失程度也会存在零丢失的情形.企业不愿意花太多的钱又要保证数据库的可靠稳定,可是苦煞了我这些搞DB的 ...

  8. RMAN catalog备份恢复方案

    对于数据库的稳定性,高可用,跨平台以及海量数据库的处理,Oracle 数据库通常是大型数据库和大企业的首选.尽管如此,仍然不乏很多中小企业想要品尝一下Oracle腥味,因此在Oracle环境中也有不少 ...

  9. 非归档模式下使用Rman进行备份和恢复

    实验环境: 一.首先进行全库数据备份: 在非归档模式下,rman备份需要在mount模式下进行 SQL> select status from v$instance; STATUS ------ ...

随机推荐

  1. threejs 限制物件只能在指定平面上拖拽

    threejs提供有 DragController.js的例子来辅助拖拽 该例子可以在基于当前屏幕的x和y轴上拖拽物体,但是它不能影响z轴. 查看代码,可以在touchStart\mousedown下 ...

  2. EF Core 中处理 1对1 关系

    最近在开发记录感想功能的时候用到了1对1的数据关系,具体情况是这样的,有这样两个1对1的类型 public class Item { public int Id { get; set; } publi ...

  3. [AI开发]DeepStream开发填坑记录

    下面是在deepstream使用过程中碰到的一些坑: (1)Pipeline中的Sink如果需要编码存文件或者推rtmp的流,注意控制编码的参数,编码质量不要太高.否则可能Sink带不动,整个Pipe ...

  4. js中数组去重方法及性能对比

    js中数组的 数组去重 常用的数组去重方法以及效率分析: 首先我们先构建一个数组,主要是用于进行去重实验,我们主要实验的量级为1000,10000,100000,500000.具体的生成数组的方法如下 ...

  5. CRC校验算法的实例解析

    概念   CRC校验算法,说白了,就是把需要校验的数据与多项式进行循环异或(XOR), 进行XOR的方式与实际中数据传输时,是高位先传.还是低位先传有关.对于数据 高位先传的方式,XOR从数据的高位开 ...

  6. 《Netty Zookeeper Redis 高并发实战》 图书简介

    <Netty Zookeeper Redis 高并发实战> 图书简介 本书为 高并发社群 -- 疯狂创客圈 倾力编著, 高度剖析底层原理,深度解读面试难题 疯狂创客圈 Java 高并发[ ...

  7. 使用Condition

    /** * ReentrantLock使用Condition对象来实现wait和notify的功能* 使用Condition时,引用的Condition对象必须从Lock实例的newCondition ...

  8. C# Task TaskFactory 异步线程/异步任务

    Task是.NetFramework3.0出现的,线程是基于线程池,然后提供了丰富的API TaskFactory  提供对创建和计划 Task 对象的支持 创建和启动异步任务 1.Task task ...

  9. 【每天一题】LeetCode 0026. 删除排序数组中的重复项

    开源地址:https://github.com/jiauzhang/algorithms 题目描述 /* * https://leetcode-cn.com/problems/remove-dupli ...

  10. config-server-bus动态更新配置

    config-server用来搭建配置中心,而配置信息一般使用gitlab仓库来存储,这样在你的配置发生改变时,不需要从新打包,而如果使用native的试,则需要从新打一个config-server的 ...