Use this procedure to configure the source and destination instances before you restore the Oracle database to a different instance.
Note
Running a cross-instance restore to a different instance on the same machine is not permitted. This prevents the accidental overwriting and resulting loss of the source database. If you want to run a restore operation to another instance on the same machine, you can use Commvault Oracle database duplication. For more information, see Database Duplication for Oracle.
Procedure
-
Create an init pfile for the destination instance.
You can either create the pfile from the spfile on the source instance and copy it over to the destination instance, or create a new init file.
Note
If Oracle Managed Files (OMF) is enabled, then an spfile must be used for the destination database. If a pfile must be used, then OMF must be turned off for the destination database.
-
Create new directories to hold the data files, control files, and the redo log files. These directories should be owned by the “oracle” user.
-
Update the init file with the new file locations.
Update the following parameters in the init file to point to these new paths:
-
<DBNAME>._ORACLE_BASE
-
*.CONTROL_FILES
-
*.AUDIT_FILE_DEST
-
*.DB_RECOVERY_FILE_DEST
-
*.DIAGNOSTIC_DEST
-
-
Place the destination instance in “NOMOUNT” mode, and then add the instance to the CommCell configuration.
If you add an entry for the new instance in the /etc/oratab file, the instance can be automatically discovered by the agent. Otherwise, you must manually add the instance to the CommCell configuration for the destination client. For instructions to add an instance manually, see Manually Adding CommCell Instances for Oracle Databases.