By default, when you restore database tables to a target instance, the system automatically duplicates the source database to an auxiliary instance in the specified temporary staging location. Once the database is duplicated, you can import the tables to the target instance.
If needed, you can also use a user-defined auxiliary instance for the restore operation. This is used when you want to restore a table to a specific failure point.
Note
When restoring tables to a different host, if a user-defined auxiliary instance option is selected for the restore, you need to recover the database to a specified point-in-time or SCN number. You cannot recover the database to the current time using a user-defined auxiliary instance.
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.
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.