Default: There is no default.
Specifies that you want to perform an import in transportable-tablespace mode over a database link (as specified with the
Syntax and Description
TRANSPORT_TABLESPACES=tablespace_name [, ...]
Because this is a transportable-mode import, the tablespaces into which the data is imported are automatically created by Data Pump.You do not need to pre-create them. However, the data files should be copied to the target database before starting the import.
When you specify
TRANSPORT_TABLESPACES on the import command line, you must also use the
NETWORK_LINK parameter to specify a database link. A database link is a connection between two physical database servers that allows a client to access them as one logical database. Therefore, the
NETWORK_LINK parameter is required because the object metadata is exported from the source (the database being pointed to by
NETWORK_LINK) and then imported directly into the target (database from which the impdp command is issued), using that database link. There are no dump files involved in this situation. You would also need to specify the
TRANSPORT_DATAFILES parameter to let the import know where to find the actual data, which had been copied to the target in a separate operation using some other means.
If you already have a dump file set generated by a transportable-tablespace mode export, then you can perform a transportable-mode import of that dump file, but in this case you do not specify
NETWORK_LINK. Doing so would result in an error. Rather, you specify the dump file (which contains the metadata) and the
TRANSPORT_DATAFILES parameter. The presence of the
TRANSPORT_DATAFILES parameter tells import that it's a transportable-mode import and where to get the actual data.
When transportable jobs are performed, it is best practice to keep a copy of the data files on the source system until the import job has successfully completed on the target system. If the import job should fail for some reason, you will still have uncorrupted copies of the data files.
You cannot export transportable tablespaces and then import them into a database at a lower release level. The target database into which you are importing must be at the same or later release level as the source database.
TRANSPORT_TABLESPACES parameter is valid only when the
NETWORK_LINK parameter is also specified.
Transportable mode does not support encrypted columns.
To use the
TRANSPORT_TABLESPACES parameter to perform a transportable tablespace import, the
COMPATIBLE initialization parameter must be set to at least 11.0.0.
Depending on your operating system, the use of quotation marks when you specify a value for this parameter may also require that you use escape characters. Oracle recommends that you place this parameter in a parameter file, which can reduce the number of escape characters that might otherwise be needed on the command line.
Transportable tablespace jobs do not support the
ACCESS_METHOD parameter for Data Pump Import.
In the following example, the
source_database_link would be replaced with the name of a valid database link. The example also assumes that a data file named
tbs6.dbf has already been copied from the source database to the local system. Suppose you have a parameter file,
tablespaces.par, with the following content:
DIRECTORY=dpump_dir1 NETWORK_LINK=source_database_link TRANSPORT_TABLESPACES=tbs_6 TRANSPORT_FULL_CHECK=NO TRANSPORT_DATAFILES='user01/data/tbs6.dbf'
You can then issue the following command:
> impdp hr PARFILE=tablespaces.par
Oracle Database Administrator's Guide for more information about database links
"Using Data File Copying to Move Data" for more information about why it's a best practice to maintain a copy of your data files on the source system