Use RMAN to copy RAC + ASM to a single instance + ASM

This test copies the dual-node RAC deployed on ASM to the ASM of a single instance. This test is also based on the needs of a project. The drill operations on the virtual machine are hereby recorded. Previously

This test copies the dual-node RAC deployed on ASM to the ASM of a single instance. This test is also based on the needs of a project. The drill operations on the virtual machine are hereby recorded. Previously

This test copies the dual-node RAC deployed on ASM to the ASM of a single instance. This test is also based on the needs of a project. We hereby record the drill operations on the virtual machine. We have already performed multiple RMAN Database Replication times. This test is characterized by copying data from RAC to a single instance. Note the following:

1. spfile parameter problems
The spfile parameter in RAC records a lot of cluster-related information and needs to be modified during replication. For example
*. Cluster_database = true
PROD2.instance _ number = 2
PROD1.instance _ number = 1
*. Remote_listener = 'Cluster-scan: 100'
PROD2.thread = 2
PROD1.thread = 1
PROD2.undo _ tablespace = 'undotbs2'
PROD1.undo _ tablespace = 'undotbs1'
You can comment out or delete RAC-related information.

2. undo tablespace Problems
The dual-node RAC backup set generates two undo tablespaces and their data files, while a single instance database only needs one undo tablespace. After the RAC backup set is restored on a single instance database, you can manually delete the redundant undo tablespace and its data files, usually undotbs2.

3. redo Problems
The redo information of two instances is recorded in the backup of the control file of the dual-node RAC. After the recovery is complete, the online redo log of thread2 is created after the open resetlogs opens the database, that is, the online log of Node 2. Same as the undotbs2 processing principle, delete it.

1. the RAC end adopts the rman full backup database to the/backup directory.

[Oracle @ node1 ~] $ Rman target/

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

Copyright (c) 1982,201 1, 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.99 m disk 00:00:04 03:05:29
BP Key: 43 Status: AVAILABLE Compressed: NO Tag: FULL
Piece Name:/backup/full_1bpjmdbl_00001.bak
List of Datafiles in backup set 43
File LV Type Ckp SCN Ckp Time Name
-------------------------------------------
2 Full 1298717 03:05:25 + DATA/prod/datafile/sysaux.257.859325451
4 Full 1298717 03:05:25 + DATA/prod/datafile/users.259.859325451
5 Full 1298717 03:05:25 + DATA/prod/datafile/example.264.859325525
6 Full 1298717 03:05:25 + DATA/prod/datafile/undotbs2.265.859325695

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

BS Key Type LV Size Device Type Elapsed Time Completion Time
-----------------------------------------------------------------
45 Full 80.00 k disk 00:00:00 03:05:32
BP Key: 45 Status: AVAILABLE Compressed: NO Tag: FULL
Piece Name:/backup/full_1epjmdbs_00001.bak <parameter file is in the backup part and needs to be used for subsequent recovery

SPFILE encoded ded: Modification time: 02:02:18
SPFILE db_unique_name: PROD

BS Key Type LV Size Device Type Elapsed Time Completion Time
-----------------------------------------------------------------
46 Full 17.80 m disk 00:00:01 03:05:33
BP Key: 46 Status: AVAILABLE Compressed: NO Tag: FULL
Piece Name:/backup/full_1dpjmdbs_20.1.bak <backup part of the control file, which must be used for subsequent recovery

Control File Included: Ckp SCN: 1298731 Ckp time: 03:05:32