Restoring Data from an Oracle Logical Dump Backup

You can restore Oracle data from a logical dump backup, to the same instance or a different instance.

Before You Begin

• The backup to be used for this restore operation must have been performed using a subclient configured for Oracle logical dump backups. For more information, see Creating a Subclient for Oracle Logical Dump Backups.

• The schema must be present on the destination before running the restore procedure. If it is not present, the database administrator must create the schema before restoring the data.

• If you will be running a cross-server restore, the connect string details of the destination database must be in the source's tnsnames.ora file and the connect string details of the source database must be in the destination's tnsnames.ora file.

Procedure

1. From the navigation pane, go to Protect > Databases.

   The database overview page appears.

2. On the Instances tab, click the instance.

   The instance page appears.

3. From the Destination server list, select the server.

4. In the Staging path box, type the full path to the location on the destination where the software stages the data before it imports the data to the database.

5. In the Parallelism for import box, type the number of streams the software uses for the restore operation.

6. If you are restoring to a different instance, complete the following steps:

   1. Select the Import to database check box.

   2. From the Database name list, select the database that the software restores the tables to.

   3. In the Connect string box, type the user name, password, and service name for the connect string for the database.

   4. If you want to restore data to different tablespaces on the destination, use the Remap tablespace box to define how you want the tablespaces remapped. The format of the string is as follows, with a space character between each source:destination pair:

      Tablespace1_source:Tablespace1_destination Tablespace2_source:Tablespace2_destination... TablespaceN_source:TablespaceN_destination
      

      Note

      If remapping of the tablespaces fails with Oracle errors, then the tablespaces cannot be remapped. If this occurs, the database administrator must create tablespaces in the destination database that are identical to those in the source database.

   5. To overwrite the existing tables on the destination, select the Overwrite if table exists check box.

7. To specify pre- or post-recovery scripts, do the following under Pre or Post options:

   1. Type the path to the script.

   2. To run a script as a specific user, move the Run as user toggle to the right and type the user name and password.

8. Click SUBMIT to start the restore.