LOG_FILE_NAME_CONVERT initialization parameters appropriately. Thus, the
target database files will not be overwritten by the duplicate database files.
Limitations
• Database duplication is not supported using proxy copy backups of the primary
database.
• 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 databases when the duplicate
database resides in the same Oracle home directory as the target database. Note
also that if the duplicate database resides in a different Oracle home directory
than the target database, then the duplicate database name has to differ from
other database names in that same Oracle home directory.
To duplicate a production database:
1. On the client where the selected database will be duplicated, put the Oracle
auxiliary database instance in the nomount state. See “Changing the database
state” on page 105.
2. In the Context List of the Data Protector GUI, click Restore.
3. Under Restore Objects, expand Oracle Server, expand the client on which the
production database resides, and then click the production database which you
want to duplicate. If there are several such clients, select the client on which you
want the Data Protector Oracle integration agent (ob2rman.pl) to be started.
4. In the Restore Action drop-down list, select Perform Duplication.
Data Protector Oracle ZDB integration116
To Next Page
Loading...
Need help?
General