RMAN Incremental backup Cloning without catalog

RMAN Cloning without catalog:

1.      Pre-cloning activities on the Source machine (adpreclone.pl on both the nodes).

2.      Take the Full Hot Backup using RMAN utilities.

3.      Copy the hot backup pieces to Target machine.

4.      Copy the binaries of both database and APPS to Target machine.

5.      Change the permission of all files according to user on Target machine.

6.      Run cloning script on DB Tier (perl adcfgclone.pl dbTechStack) on Target machine.

7.      Add new configuration parameters in init$ORACLE_SID.ora

8.      Startup the database in nomount state.

9.      Register the full backup pieces and incremental backup pieces with Catalog.

10.  Restore the Database full database backup pieces.

11.  Recover the Database using incremental backup pieces.

12.  Add tempfile to existing TEMP tablespace.

13.  Down the listener and Database.

14.  Run cloning script on DB Tier (perl adcfgclone.pl dbTier) on Target machine.

15.  Perform the post cloning activities.

Grep the below data from source.

select 'set newname for datafile '|| file_id ||' to '||''''||'/data1/OBADATA'||file_name||''';' from dba_data_files;

Add the below parameter into  the pfile of target:

Leve-1 backup recovery:

Register the backup pieces.

Change the Database name by using the NID Utility:

Note: Please check temp files.

run the new source database environment variables.

Relation between RMAN retention period and control_file_record_keep_time

Relation between RMAN retention period and control_file_record_keep_time:( Doc ID: 397269.1)

RMAN backup keeps the backup metadata information in the reusable section of the controlfile. It depends on the parameter CONTROL_FILE_RECORD_KEEP_TIME. CONTROL_FILE_RECORD_KEEP_TIME specifies the minimum number of days before a reusable record in the control file can be reused. In the event a new record needs to be added to a reusable section and there is not enough space then it will delete the oldest record, which are aged enough. 

Backup retention policy is the rule to set regarding which backups must be retained (whether on disk or other backup media) to meet the recovery and other requirements. 

If the CONTROL_FILE_RECORD_KEEP_TIME is less than the retention policy then it may overwrite reusable records prior to obsoleting them in the RMAN metadata. Therefor it is recommended that the CONTROL_FILE_RECORD_KEEP_TIME should set to a higher value than the retention policy. 

Formula 

CONTROL_FILE_RECORD_KEEP_TIME = retention period + level 0 backup interval + 1 

For e.g. 

e.q. level 0 backup once a week with retention policy of a recovery windows of 14 days then in this case the CONTROL_FILE_RECORD_KEEP_TIME should be 14+7+1=22