Duplicate Database Using TARGETLESS RMAN Connection

Source DB: orasbt1

Target DB: orasbp1

Catalog DB: RMANDB

DB Version: 11.2.0.1 for all 3 databases

ASM DiskGroups: (optional)

DATA: For datafile and online redo logs

REDO: For archivelog location

OBACK: For RMAN Backup location

Migrate Oracle Database from Non-ASM to ASM Using RMAN

We need to modify the spfile of the target database as follows:                                

1. Disable block change tracking. (In case you have Block Change Tracking enabled)
2. Modify DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n and CONTROL_FILES parameter to appropreiate ASM Disk Groups

SQL> ALTER DATABASE DISABLE BLOCK CHANGE TRACKING; --optional           
                                                                        
SQL> ALTER SYSTEM SET db_create_file_dest='+DATA' SCOPE=SPFILE;         
SQL> ALTER SYSTEM SET db_create_online_log_dest_1='+DATA' SCOPE=SPFILE; 
SQL> ALTER SYSTEM SET db_create_online_log_dest_2='+DATA' SCOPE=SPFILE; 
SQL> ALTER SYSTEM SET db_create_online_log_dest_3='+DATA' SCOPE=SPFILE;
SQL> ALTER SYSTEM SET control_files='+DATA' SCOPE=SPFILE;

Duplicate Database on Same Server & Same ORACLE_HOME Using RMAN in 10 Steps

This Duplication Process is applicable where Source DB is in Archivelog Mode or Noarchivelog Mode. Ensure we have RMAN backups of source DB. Also if Catalog DB is not available, RMAN will use controlfile instead.

Source DB: COSP1

Target DB: COSP1BK

Catalog DB: RMANDB

DB Version: 11.2.0.1 for all 3 databases

Block Change Tracking

Block Change Tracking is an option to track datafile blocks affected by each database update. The tracking information is stored in a block change tracking file. When block change tracking is enabled, RMAN uses this file, to read those changed blocks. This improves incremental backup performance, as it saves time from reading all the data files for changed blocks. CTWR process logs the changed blocks to block change tracking file.

How to enable block change tracking

SQL> ALTER DATABASE ENABLE BLOCK CHANGE TRACKING USING FILE '/oradata/cost1/cost1TF.log';

How to disable block change tracking

SQL> ALTER DATABASE DISABLE BLOCK CHANGE TRACKING;

Monitor Block Change Tracking file

SQL> set lines 100

SQL> col filename for a45

SQL> select * from v$block_change_tracking;

Configure Backup Path

Configure Controlfile backup path for RMAN:-

RMAN> configure controlfile autobackup format for device type disk to '/u02/app/oracle/oradata/cosp1/cf_backup/cf_%F';

Configure Datafile backup path for RMAN:-

RMAN> configure channel device type disk format '/u02/app/oracle/oradata/cosp1/df_backup/ora_df%t_s%s_s%p';

Connect to Target database and Catalog Database at the same time

Set the environment variable for target database. To check whether you have set the variables correctly, log into sqlplus to verify;

SQL> select name, open_mode from v$database;

NAME      OPEN_MODE
--------- --------------------
COSP1      READ WRITE