HP A.06.11 - Manual (Page 110)

If the archived redo logs required for recovery are accessible on disk, restore only
damaged datafiles and restart redo apply process.
If you have lost the entire standby database, it is better to perform duplication of the
database (unless only a few damaged datafiles or tablespaces need to be restored).
Perform duplication of the database also when:
• Primary database control file was restored or recreated.
• Point-in-time recovery was performed on the primary database.
• Failover of database roles occurred.
Duplicating an Oracle database
Perform a production database duplication to create:
• A standby database which has the same DBID as the production (primary)
database. With this, you can:
• Create a new standby database.
• Re-create a standby database after:
• Loss of entire standby database
• Primary database control file was restored or recreated
• Database point-in-time recovery was performed on the primary database
• Switchover or failover of database roles occurred
• An independent copy, with a unique DBID, which can be used for data mining
or testing purposes.
Prerequisites
• The whole primary database with the archived logs must be backed up.
• Archive logs, which have not been backed up to tape since the last full backup
and are required for duplication must be available on the duplicate system with
the same path names as on the target system (system with the production database
to be duplicated).
• Net service name for the auxiliary instance must be configured.
• When duplicating a database on the same system on which the target database
resides, set all *_PATH, *_DEST, DB_FILE_NAME_CONVERT, and
LOG_FILE_NAME_CONVERT
initialization parameters appropriately. Thus, the
target database files will not be overwritten by the duplicate database files.
Integrating Oracle and Data Protector 110