Creating a Duplicate Database on a New Host (non ASM).
(Doc ID 388431.1)
Last updated on MARCH 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124.0 [Release 9.0.1 to 19]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database 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.
***Checked for relevance on 06-Aug-2009***
***Checked for relevance on 01-Feb-2011***
***Checked for relevance on 21-May-2015***
The following note will guide a user in creating a duplicate database on a new host (non ASM). The scenario refers to a recovery catalog however a catalog is not mandatory. The following example has been completed on a linux operating system.
The note is applicable for 9i, 10g and 11g. However 11g has new features of the duplicate command, see further details in the following articles:
<Note 452868.1> RMAN 'Duplicate From Active Database' Feature in 11G
<Note 1375864.1> Perform Backup Based RMAN Duplicate Without Connecting to a Target Database for Both Disk & Tape Backups (available in 11.2 and beyond)
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
|Duplicate database from server A to server B (Non ASM)|
|1. Backup of the primary database.|
|2. Determine how much disk space will be required.|
|3. Ensuring you have enough space on your target server.|
|4. Making the backup available for the duplicate process.|
|5. Creating the init.ora & administration directories for the duplicate database.|
|6. Ensuring SQL*NET connections to primary database and RMAN catalog are working.|
|7. Prepare RMAN duplicate script.|
|8. Execute the RMAN script.|