Tuning RMAN - duplicate active database with size 1.7TB
Dear Oracle experts!
We are going to have a project where we will migrate an ERP standalone database to RAC cluster database.
The source standalone db version is 11gR3 with the latest PSU patch.
The target database would be on the same version on a RAC cluster with ASM.
Of course we want to use RMAN for duplication. The source box and the target cluster nodes are different physical servers.
Being given that the database is around 1.7TB, I would like to ask you some kind of best practices what rman options we can leverage having less time for the actual data migration. In the past I did several RAC migration with 4 allocated channels. Here is a sample for the RMAN script:
run
{
allocate channel dev1 device type disk;
allocate channel dev2 device type disk;
allocate channel dev3 device type disk;
allocate channel dev4 device type disk;
allocate auxiliary channel dev5 device type disk;
allocate auxiliary channel dev6 device type disk;
allocate auxiliary channel dev7 device type disk;
allocate auxiliary channel dev8 device type disk;
duplicate target database to NEW_RAC
from active database
password file
spfile
set control_files='+FRA_DG/NEW_RAC/controlfile/control01.ctl','+DATA_DG/NEW_RAC/controlfile/control02.ctl'
set db_create_file_dest='+DATA_DG'
set db_create_online_log_dest_1='+FRA_DG'
set db_recovery_file_dest='+FRA_DG'
set db_recovery_file_dest_size='1G';
}
Of course there are many pre and post steps like configuring tnsnames for rman then creating undo tablespaces, rac services etc. I would like to ask you to focus on the main data migration part and let me know your suggestions.
Thank you in advance,
Laszlo