Perform Backup Based RMAN DUPLICATE Without Connecting To Target Database For Both Disk & Tape Backups

(Doc ID 1375864.1)

Last updated on JANUARY 12, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterInformation in this document applies to any platform.
*** Check on currency 10-Dec-2015 ***

Goal

If you are performing a backup based RMAN duplicate and using a recovery catalog as well, it is not required to connect to the source database as TARGET in RMAN.

This technique is advantageous where network connections from the auxiliary host to the source database are restricted or prone to intermittent disruptions. In duplication without a TARGET connection, the source database is unaffected by the duplication.

For this RMAN duplication, we will connect rman to the auxiliary instance and recovery catalog database and run duplicate command similar to below:

a) We can use this technique for both disk as well as tape (sbt) backups.

b) Use of recovery catalog is mandatory

c) If you do not have a recovery catalog, you can still perform RMAN DUPLICATE without connecting to the target database but ONLY for disk backups. This is achieved via BACKUP LOCATION clause of DUPLICATE command i.e.

Below document has more details for this procedure:(Doc ID 874352.1) RMAN 11GR2 : DUPLICATE Without Target And Recovery Catalog Connection

#

Additional Note: Targetless DUPLCIATE at same HOST as TARGET

If you are using TARGETLESS Duplicate using 'BACKUP LOCATION' on the same Host/Node as the Target exist Then you must make sure that no existing files from TARGET are overwritten. This is done by CONVERT Parameters as shown, but you must also ensure to get controlfile to a unique location so using -> set control_files='<unique-path-location-name>' in SPFILE clause . Otherwise it is possible that this error might be encountered because rman will restore the spfile and then the control_files setting would point to the source/target db controlfile: