Standby Creation using RMAN DUPLICATE Without Target And Recovery Catalog Connection
(Doc ID 2011015.1)
Last updated on APRIL 04, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
Goal
Disclaimer:
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Primary Database:Chicago
Standby database: Boston
Starting with RMAN11g Release 2 (11.2) RMAN is able to execute the duplicate command without connecting to the target database. For disk backups, a recovery catalog is also not necessary. However, if backups are on tape a recovery catalog is required.
The information in this article will focus on disk backups and running duplicate with only an auxiliary connection.
To complete an rman duplicate with only an auxiliary connection (no target and no catalog), rman needs the location of the backup sets which should be available on the auxiliary server. RMAN reads the backup pieces and restores the spfile,controlfile,datafiles and archivelog files to complete the duplicate operation.
An example for this kind of duplicate operation is:
Solution
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
| Goal |
| Solution |
| References |