本次试验将部署到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