Using the Transportable Option During Full Mode Exports
If you specify the
TRANSPORTABLE=ALWAYS parameter along with the
FULL parameter, then Data Pump performs a full transportable export. A full transportable export exports all objects and data necessary to create a complete copy of the database. A mix of data movement methods is used:
Objects residing in transportable tablespaces have only their metadata unloaded into the dump file set; the data itself is moved when you copy the data files to the target database. The data files that must be copied are listed at the end of the log file for the export operation.
Objects residing in non-transportable tablespaces (for example,
SYSAUX) have both their metadata and data unloaded into the dump file set, using direct path unload and external tables.
Performing a full transportable export has the following restrictions:
The user performing a full transportable export requires the
The default tablespace of the user performing the export must not be set to one of the tablespaces being transported.
If the database being exported contains either encrypted tablespaces or tables with encrypted columns (either Transparent Data Encryption (TDE) columns or SecureFiles LOB columns), then the
ENCRYPTION_PASSWORD parameter must also be supplied.
The source and target databases must be on platforms with the same endianness if there are encrypted tablespaces in the source database.
If the source platform and the target platform are of different endianness, then you must convert the data being transported so that it is in the format of the target platform. You can use the
DBMS_FILE_TRANSFER package or the
CONVERT command to convert the data. See Oracle Database Administrator's Guide for more information about using either of these options.
A full transportable export is not restartable.
All objects with storage that are selected for export must have all of their storage segments either entirely within administrative, non-transportable tablespaces (
SYSAUX) or entirely within user-defined, transportable tablespaces. Storage for a single object cannot straddle the two kinds of tablespaces.
When transporting a database over the network using full transportable export, tables with
RAW columns that reside in administrative tablespaces (such as
SYSAUX) are not supported.
When transporting a database over the network using full transportable export, auditing cannot be enabled for tables stored in an administrative tablespace (such as
SYSAUX) if the audit trail information itself is stored in a user-defined tablespace.
If both the source and target databases are running Oracle Database 12c Release 1 (12.1), then to perform a full transportable export, either the Data Pump
VERSION parameter must be set to at least 12.0. or the
COMPATIBLE database initialization parameter must be set to at least 12.0 or later.
Full transportable exports are supported from a source database running release 18.104.22.168. To do so, set the Data Pump
VERSION parameter to at least 12.0 as shown in the following example:
> expdp user_name FULL=y DUMPFILE=expdat.dmp DIRECTORY=data_pump_dir TRANSPORTABLE=always VERSION=12.0 LOGFILE=export.log