> CommCell Console > Backup and Restore Agents > Databases > Oracle > Oracle Backup Administrator Guide > Oracle Restores > Oracle Table Restores > Restoring a Table in a CDB

Restoring an Oracle Table in a CDB to a Different Location (Out of Place)

You can restore Oracle tables in container databases (CDBs) to a different location if some of the tables in the Oracle database are lost or corrupted.

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 TTS failures that happen when the target connection occurs.

This procedure does not require an auxiliary instance for the destination.

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

  • Configure Oracle Subclients for Table Level Restores.

  • Perform a full backup of the subclient.

  • If the tables contain non-English characters, see Restoring Tables with Non-English Characters for Oracle.

  • 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.

  • 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 are going to use a table import for restoring tables, the destination instance connect string must have sysdba privileges.

  • Verify the following configuration:

    • The source and destination hosts have the same schema

    • The source and destination clients use a different connection name in the tnsnames.ora file

    • The database names in the table are included in the files

      Database Name

      tnsnames.ora on source

      tnsnames.ora on destination

      listner.ora on destination

      duplicate database name

      √

      √

      √

      source database name

      √
    Example

    The following are examples of the tnsnames.ora files for the source and destination clients. The source database name is db1_table and the destination database name is db1.

    Source client tnsnames.ora file

    db1_table =
(DESCRIPTION = 
(ADDRESS = (PROTOCOL = TCP)(HOST = M1)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = db1)
)
)

    Destination client tnsnames.ora file

    db1 = 
(DESCRIPTION = 
(ADDRESS = (PROTOCOL = TCP)(HOST = M2)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = db1)
) 
)

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Oracle.

  2. Right-click the instance, point to All Tasks and then select Browse and Restore.

  3. Select the Table View check box and click View Content.

  4. To display the list of PDBs, in the browse window click the + to the left of the instance name.

    The list of PDBs appears.

  5. To display the list of schemas, in the browse window click the + to the left of the PDB name.

    The list of schemas appears.

  6. To display the list of tables, in the browse window click the schema.

    The list of tables appears.

  7. 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.

  8. Select the tables and then click Recover All Selected.

    The table restore options dialog box appears.

  9. To specify the destination client, on the General tab, in the Destination Client box, select the destination client.

    The destination client can be the original source client or a different client.

  10. 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, select Dump, and then from the Use Oracle settings from list select the instance.

    • To overwrite the current tables, select Import and from the Import Destination list select the destination instance.

  11. If you specified the Import option to overwrite the current tables and want to select a destination PDB, select the Source PDB, and then from the Destination PDB list select a destination PDB.

  12. 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.

  13. 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.

  14. Click OK.

Page contents

×

Loading...