RMAN 11GR2 : DUPLICATE Without Target And Recovery Catalog Connection
(Doc ID 874352.1)
Last updated on JULY 31, 2019
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 10-Dec-2015***
Rman 11g release 2 provides us the flexibility of creating the rman duplicate without connecting to the target database and recovery catalog.
All rman needs here is the location of the backup pieces which is accessible and rman reads the backup pieces and restores the spfile,controlfile,datafiles and archivelog files to perform the duplicate operation.
An example for this kind of duplicate operation is:
RMAN> DUPLICATE DATABASE TO <auxiliary DB name>
UNTIL TIME "TO_DATE('29-MAY-2010 14:16:42','DD-MON-YYYYHH24:MI:SS')"
set control_files='D:\<aux path>\c1.ctl'
set db_file_name_convert='D:<target path>','D:<aux path>'
set log_file_name_convert='D:<target path>','D:<aux path>'
BACKUP LOCATION 'D:\<location of backup on disk>';
# Here use of the BACKUP LOCATION clause identifies the type of duplication as having no target connection, no recovery catalog and being backup-based.
Oracle® Database Backup and Recovery User's Guide
11g Release 2 (11.2)
What's New in Backup and Recovery?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Process involved in this type of duplicate database|
|The steps involved in creating the duplicate database are as follows|