欢迎您访问程序员文章站本站旨在为大家提供分享程序员计算机编程知识!
您现在的位置是: 首页  >  数据库

使用RMAN将RAC+ASM复制到单实例+ASM上

程序员文章站 2022-04-24 19:21:45
...

本次试验将部署到ASM上的双节点RAC复制到单实例的ASM上。该试验也是出自于一个项目的需求,在虚拟机上演练操作特此记录。之前已经

本次试验将部署到ASM上的双节点RAC复制到单实例的ASM上。该试验也是出自于一个项目的需求,,在虚拟机上演练操作特此记录。之前已经做过多次RMAN复制数据库,这次试验的特点是从RAC复制到单实例。需要注意的以下内容:

1,spfile参数问题
RAC下的spfile参数中记录了很多和集群相关的信息,在复制时需要修改。比如
*.cluster_database=true
PROD2.instance_number=2
PROD1.instance_number=1
*.remote_listener='cluster-scan:1521'
PROD2.thread=2
PROD1.thread=1
PROD2.undo_tablespace='UNDOTBS2'
PROD1.undo_tablespace=‘UNDOTBS1’
和RAC相关的信息可以选择注释掉,或者删除。

2,undo表空间问题
双节点RAC的备份集中会产生2个undo表空间及其数据文件,而单实例数据库只需要一个undo表空间。使用RAC的备份集在单实例数据库上恢复后,可以手工删除多余的那个undo表空间及其数据文件,通常是undotbs2

3,redo问题
双节点RAC的控制文件的备份中记录的是两个实例的redo信息,恢复完成后在open resetlogs打开数据库后回创建出thread2的online redo log,也就是节点2的联机日志。同undotbs2的处理原则一样,删除之。


1,RAC 端rman全备数据库到/backup目录下。

[Oracle@node1 ~]$ rman target /

Recovery Manager: Release 11.2.0.4.0 - Production on Mon Sep 29 03:15:49 2014

Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

connected to target database: PROD (DBID=271163854)

RMAN> run{
2> allocate channel c1 type disk;
3> allocate channel c2 type disk;
4> backup tag 'full' format '/backup/full_%U.bak'
5> database include current controlfile;
6> sql 'alter system archive log current';
7> backup tag 'arch' format '/backup/arch_%U.arc'
8> archivelog all;
9> release channel c1;
10> release channel c2;
11> }

RMAN> list backup;

List of Backup Sets
===================

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
43 Full 522.99M DISK 00:00:04 2014-09-29 03:05:29
BP Key: 43 Status: AVAILABLE Compressed: NO Tag: FULL
Piece Name: /backup/full_1bpjmdbl_1_1.bak
List of Datafiles in backup set 43
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- ------------------- ----
2 Full 1298717 2014-09-29 03:05:25 +DATA/prod/datafile/sysaux.257.859325451
4 Full 1298717 2014-09-29 03:05:25 +DATA/prod/datafile/users.259.859325451
5 Full 1298717 2014-09-29 03:05:25 +DATA/prod/datafile/example.264.859325525
6 Full 1298717 2014-09-29 03:05:25 +DATA/prod/datafile/undotbs2.265.859325695

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
44 Full 649.16M DISK 00:00:04 2014-09-29 03:05:29
BP Key: 44 Status: AVAILABLE Compressed: NO Tag: FULL
Piece Name: /backup/full_1cpjmdbl_1_1.bak
List of Datafiles in backup set 44
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- ------------------- ----
1 Full 1298719 2014-09-29 03:05:25 +DATA/prod/datafile/system.256.859325451
3 Full 1298719 2014-09-29 03:05:25 +DATA/prod/datafile/undotbs1.258.859325451
7 Full 1298719 2014-09-29 03:05:25 +DATA/prod/datafile/goldengate.269.859338811

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
45 Full 80.00K DISK 00:00:00 2014-09-29 03:05:32
BP Key: 45 Status: AVAILABLE Compressed: NO Tag: FULL
Piece Name: /backup/full_1epjmdbs_1_1.bak

SPFILE Included: Modification time: 2014-09-29 02:02:18
SPFILE db_unique_name: PROD

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
46 Full 17.80M DISK 00:00:01 2014-09-29 03:05:33
BP Key: 46 Status: AVAILABLE Compressed: NO Tag: FULL
Piece Name: /backup/full_1dpjmdbs_1_1.bak

Control File Included: Ckp SCN: 1298731 Ckp time: 2014-09-29 03:05:32