rman deplicate（RMAN deplicate）.docVIP

rman deplicate（RMAN deplicate） Using the RMAN DUPLICATE command, you can create a replica database (Duplicate, D, atabase) based on the backup of the target database (Target, D, atabase) on the basis of the retention of the target database. The replica can be exactly the same as the target database, or only a subset of the target database table space. Target sites (Target, Site) and replica sites (Duplicate, Site) can even be on the same machine. The replica database is a copy of the target database, just like our clone database Test backup and recovery process. Export data, such as a table that is intentionally or unintentionally deleted from the production database, and then you can import it into the production database. First, you need to create a helper instance (auxiliary, instance) Through RMAN, you must be able to connect to the target database and start the auxiliary instance in the nomount mode. Then, at least one auxiliary channel is allocated on the auxiliary instance, and the main work of replication is implemented by the auxiliary channel of the server session initiated at the replica site. Then apply the necessary backup of the main library, and create and restore the copy database. The RMAN client can run anywhere, as long as it can connect to the primary and secondary instances. All backups that can be accessed by replica sites, and archived redo logs, will be used to create and restore replica databases. If you use disk backups, you can make sure the path is available by: Manually copy the same path to backup the source site to the remote site. For example, the backup file for the source site is under d:\oradata\bkp, and is copied to the replica site and copied to the d:\oradata\bkp directory. This is important, because when two machines are out, many people often forget the COPY backup files to the secondary database and cause the DUPLICATE to fail Manually backup the new path from the source site to the replica site. For example, the backup file