Integrating Oracle and Data Protector

Restoring an Oracle 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.

Limitation

• Database duplication is not supported using proxy copy backups of

 

the primary database.

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.

Limitations

• If you perform duplication of a database (not for standby) on the same

 

system on which the target or production database resides, note that

 

you cannot use the same database name for the target and duplicate

Chapter 1

85