See Also:Oracle Database Backup and Recovery User's Guide to learn how to transport tablespaces with RMAN
The limitations on creating transportable tablespace sets described in Oracle Database Administrator's Guide apply to transporting tablespaces from backup, with the exception of the requirement to make the tablespaces read-only.
Note that the
SYSAUX tablespace must not be part of the recovery set, which is the set of tablespaces to be transported. RMAN enforces inclusion of the
SYSAUX tablespace in the auxiliary set, which contains datafiles and other files required for the tablespace transport.
TRANSPORT TABLESPACE does not convert endian formats. If the target platform has a different endian format, then after running
TRANSPORT TABLESPACE use the
CONVERT command to convert the endian format of the transportable set datafiles.
If you drop a tablespace, then you cannot later use
TRANSPORT TABLESPACE to include this tablespace in a transportable tablespace set, even if the SCN for
TRANSPORT TABLESPACE is earlier than the SCN at which the table was dropped. If you rename a tablespace, then you cannot use
TRANSPORT TABLESPACE to create a transportable tablespace set as of a point in time before the tablespace was renamed.
You must have a backup of all needed tablespaces (including those in the auxiliary set) and archived redo logs needed to recover to the target point in time.
If you do not use a recovery catalog, and if the database has re-used control file records containing metadata about required backups, then the command fails because RMAN cannot locate the backups. You may be able to use
CATALOG to add the needed backups to the RMAN repository if they are still available, but if the database is already overwriting control file records you may lose records of other needed backups.
Because the RMAN uses the Data Pump Export and Import utilities, you cannot use
TRANSPORT TABLESPACE if the tablespaces to be transported use
XMLType. In this case you must use the procedure in Oracle Database Administrator's Guide.
If a file under the name of the export dump file already in the tablespace destination, then
TRANSPORT TABLESPACE fails when it calls Data Pump Export. If you are repeating a previous
TRANSPORT TABLESPACE job, then make sure to delete the previous output files, including the export dump file.
The following database encryption features both use the wallet: transparent data encryption, which functions at the column level, and tablespace encryption. Note the following restrictions for tablespaces that are encrypted or contain encrypted columns:
If you are transporting an encrypted tablespace, then you must manually copy the wallet to the destination database.
If the destination database has an existing wallet, then you cannot copy the wallet from the source database to the destination database. Thus, you cannot transport encrypted data to a database that already has a wallet. If you encrypt columns with transparent data encryption, then you can export them into an export file that is password-protected and import the data into the destination database.
See Also:Oracle Database Advanced Security Administrator's Guide to learn about transparent data encryption
Because RMAN creates the automatic auxiliary instance used for restore and recovery on the same node as the source instance, there is some performance overhead during the operation of the
TRANSPORT TABLESPACE command.
If RMAN is not part of the backup strategy for your database, then you can still use
TRANSPORT TABLESPACE as long as the needed datafile copies and archived logs are available on disk. Use the
CATALOG command to record the datafile copies and archived logs in the RMAN repository. You can then use
TRANSPORT TABLESPACE. You also have the option of using RMAN to back up your database specifically so you can use
||Specifies the name of each tablespace to transport.
You must have a backup of all needed tablespaces (including those in the auxiliary set) and archived redo log files available for use by RMAN that can be recovered to the target time for the
This subclause specifies optional parameters that affect the tablespace transport.
||Specifies the location for files for the auxiliary instance.
You can use
See Also: Oracle Database Backup and Recovery User's Guide for details on the interactions among the different techniques for naming the auxiliary instance files
||Specifies a database directory object where Data Pump Export outputs are created (see Example 2-152). If not specified, then RMAN creates files in the location specified by
See Also: Oracle Database Utilities for more details on Data Pump Export and database directory objects
||Specifies where to create the Data Pump Export dump file. If not specified, the export dump file is named
Note: If a file under the name of the export dump file already in the tablespace destination, then
||Specifies the location of the log generated by Data Pump Export. If omitted, the export log is named
||Specifies the filename for the sample input script generated by RMAN for use in plugging in the transported tablespace at the destination database. If omitted, the import script is named
||Specifies the location of the datafiles for the transported tablespaces after the tablespace transport operation completes.|
||Specifies a restore point for tablespace restore and recovery, with the SCN at which the restore point was created as the upper, inclusive limit. Because the limit is inclusive, RMAN selects only files that can be used to restore or recover tablespaces up to and including the SCN corresponding to the restore point.|
||Specifies a past time, SCN, or log sequence number (see Example 2-151). If specified, RMAN restores and recovers the tablespaces at the auxiliary instance to their contents at that past point in time before export.
If you rename a tablespace, then you cannot use this command to create a transportable tablespace set as of a point in time before the tablespace was renamed. RMAN has no knowledge of the previous name of the tablespace.
Tablespaces including undo segments as of the
In this example, the tablespaces for the transportable set are
tools, the transportable set files are to be stored at
/disk1/transport_dest, and the transportable tablespaces are to be recovered to a time 15 minutes ago:
TRANSPORT TABLESPACE example, tools TABLESPACE DESTINATION '/disk1/transportdest' AUXILIARY DESTINATION '/disk1/auxdest' UNTIL TIME 'SYSDATE-15/1440';
Partial sample output follows:
Creating automatic instance, with SID='egnr' initialization parameters used for automatic instance: db_name=PROD compatible=11.0.0 db_block_size=8192 . . . starting up automatic instance PROD . . . executing Memory Script executing command: SET until clause Starting restore at 07-JUN-07 allocated channel: ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: SID=44 device type=DISK channel ORA_AUX_DISK_1: starting datafile backup set restore channel ORA_AUX_DISK_1: restoring control file . . . output file name=/disk1/auxdest/cntrl_tspitr_PROD_egnr.f Finished restore at 07-JUN-07 sql statement: alter database mount clone database sql statement: alter system archive log current sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end; starting full resync of recovery catalog full resync complete . . . executing Memory Script . . . Starting restore at 07-JUN-07 using channel ORA_AUX_DISK_1 channel ORA_AUX_DISK_1: starting datafile backup set restore channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set channel ORA_AUX_DISK_1: restoring datafile 00001 to /disk1/auxdest/TSPITR_PROD_EGNR/datafile/o1_mf_system_%u_.dbf datafile 1 switched to datafile copy . . . starting media recovery . . . Finished recover at 07-JUN-07 database opened . . . executing Memory Script . . . sql statement: alter tablespace EXAMPLE read only Removing automatic instance shutting down automatic instance Oracle instance shut down Automatic instance removed auxiliary instance file /disk1/auxdest/cntrl_tspitr_PROD_egnr.f deleted . . .
This example illustrates the use of the optional arguments that control the locations of Data Pump-related files such as the dump file. Note that the
DATAPUMP DIRECTORY must refer to an object that exists in the target database. Use the
CREATE DIRECTORY SQL statement to create a directory object.
TRANSPORT TABLESPACE example TABLESPACE DESTINATION '/disk1/transportdest' AUXILIARY DESTINATION '/disk1/auxdest' DATAPUMP DIRECTORY mypumpdir DUMP FILE 'mydumpfile.dmp' IMPORT SCRIPT 'myimportscript.sql' EXPORT LOG 'myexportlog.log';