Rman_ Study notes 5_rman Duplicate copy

Ready to be sorted

For a version upgrade of a database based on a production environment or to test the performance and impact of a new application, backup recovery, and so on, we can clone it locally from the production environment without affecting the normal use of the production database. We can do this by using the Rman duplicate method and its simple way. Unlike OS-level backups, the duplicate method generates a new dbid for the secondary database (the cloned database) and the ability to register both the target database (the original database) and the secondary database to the same recovery directory. This article describes the implementation of a heterogeneous database clone using Rman duplicate.



1. Duplicate type supported by Rman
Support for backup-based duplicate, which is divided into target db and not connected to the target DB, not connected to the target DB is also connected to the catalog and not connected catalog
Supports the duplicate method based on the active database. For more information about duplicate and duplicate steps, refer to: Rman-based clone of the same machine database
Both of these methods can be described briefly in the following illustration.

From Active DB
--------------
| With Recovery catalog connection
Duplicate | |--------------------------------
------------| Without target Conenction |
| |----------------------------|
|                            | |
--------------| |-------------
From Backups | Without recovery catalog connection
|-----------------------------
With Target connection



2, Rman machine recovery
The following illustration is not connected to the target DB, nor is it connected to the Recover catalog mode. To implement duplicate this way, you should specify where the backup files are located.
The experiment shown below is also based on the way that, during the demo process, the disk path, directory, and data files use the same location as the file name.
For different locations of the duplicate situation, the file location needs to be converted, reference: RMAN database Clone file Location conversion method

Rman_ Study notes 5_rman Duplicate copy