You can restore Oracle tables in container databases (CDBs) when you need to recover tables that have been logically corrupted or lost or after the table structure was modified.
By default, when you restore tables to the source database, the restore operation overwrites the existing tables in the destination database.
Best Practice: Use the Oracle catalog when you perform a table-level restore on Oracle 11g or a more recent version. The restore needs the catalog in order to skip Oracle TNS failures that happen when the target connection occurs.
In order to successfully import the tables, you must have a user that has the dba privilege, or the user must own the full table. You cannot have a user with the sysbackup privilege for the import.
On Windows configurations, the Oracle home user that you use for the Oracle instance must have the same credentials and password as the local administrator, when the local administrator is configured for the Commvault Oracle instance properties.
Before You Begin
-
Perform a full backup of the subclient.
-
If the tables contain non-English characters, see Restoring Tables with Non-English Characters for Oracle.
-
The PDBs containing the tables you want to restore must have been in an open state when you ran the backup.
-
If you are restoring tables using the control file, the source PDB must be open. If you are restoring using the catalog, the source PDB does not need to be open.
-
Indexing must be enabled. If you have a client that uses Indexing Version 1, you can upgrade it using the Upgrade To Indexing V2 workflow.
-
If you use an auxiliary instance, you can avoid problems with the auxiliary database not starting because it is using default PFILE parameters. For more information, see Defining Oracle Parameters for an Auxiliary PFILE.
Procedure
-
From the CommCell Browser, expand Client Computers > client > Oracle.
-
Right-click the instance, point to All Tasks and select Browse and Restore.
-
Select the Table View check box and click View Content.
-
To display the list of PDBs, in the browse window click the + to the left of the instance name.
The list of PDBs appears.
-
To display the list of schemas, in the browse window click the + to the left of the PDB name.
The list of schemas appears.
-
To display the list of tables, in the browse window click the schema.
The list of tables appears.
-
You can include or exclude any of the following tables in the restore: dependent tables, referenced tables, and recursively dependent tables. To do this, right-click the table and choose whether to include or exclude dependent or referenced tables.
When you restore a table which is dependent on another table due to referential constraints, you must take one of the following actions to make sure the referential integrity of the tables is maintained when the restore is complete:
-
Manually select the referenced tables.
-
Use the user interface option to select all the referenced tables.
If you select only the dependent table, the referential integrity of the tables is not maintained.
-
-
Select the tables and then click Recover All Selected.
The table restore options dialog box appears.
-
On the General tab, specify whether the restore only puts the exported tables in the staging location or overwrites the current tables:
-
To save the table export dump files to the staging location, click Dump.
-
To overwrite the current tables, click Import.
-
-
To specify the location where the auxiliary instance is created, on the Table Restore tab in the Staging Path box type the location.
The staging path must have enough free space for the control file, the Oracle diagnostic directory, and the required tablespaces.
-
If you specified the Import option to overwrite the current tables and you want to delete the tables prior to the restore, on the Advanced Options tab, select Drop Table for Import.
-
Click OK.