You can restore Oracle tables in container databases by using the RMAN command line.
Before You Begin
On Windows, the Oracle OS "oracle" user or the user that owns the oracle service must have write permissions to Windows event logs and to the auxiliary path specified in the RMAN script. For Unix, the "oracle" OS user must be able to write to the staging path.
Procedure
Use automatic channel allocation using the CONFIGURE CHANNEL command and do not allocate channels within the run block. You can use multiple channels for parallelism to improve performance.
Sample RMAN Script for Unix
Connect to RMAN and run commands similar to the following, outside the run block. Substitute any required or optional Oracle SBT parameters.
configure channel device type 'sbt_tape' PARMS="SBT_LIBRARY=$[/opt/commvault/Base/libobk.so],ENV=(CvInstanceName=$[Instance001])";
configure device type ‘sbt_tape’ parallelism $[4];
The following is the run block syntax:
run { RECOVER $[schema_name].$[table_name] OF PLUGGABLE DATABASE $[pluggable_db_name] UNTIL SCN $[scn] AUXILIARY DESTINATION '$[staging_path]’; }
The following is an example run block:
run {
RECOVER TABLE $[USERX.USERX_TABLE1] OF PLUGGABLE $[DATABASE srcpdb1]
UNTIL SCN $[10392707]
AUXILIARY DESTINATION '$[/home/oracle/staging_path]';
}
Sample RMAN Script for Windows
Connect to RMAN and run this command outside the run block:
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM $[4]
The following is an example run block:
run {
RECOVER TABLE $[PDBORA2_USER1.TAB1] OF PLUGGABLE $[DATABASE pdbora2]
UNTIL SCN $[1516408]
AUXILIARY DESTINATION '$[E:\staging]';
}
Note
Two command line restore jobs are invoked when you create and recover the automatic auxiliary instance.