A full import is specified using the
FULL parameter. In full import mode, the entire content of the source (dump file set or another database) is loaded into the target database. This is the default for file-based imports. You must have the
DATAPUMP_IMP_FULL_DATABASE role if the source is another database containing schemas other than your own.
Cross-schema references are not imported for non-privileged users. For example, a trigger defined on a table within the importing user's schema, but residing in another user's schema, is not imported.
DATAPUMP_IMP_FULL_DATABASE role is required on the target database and the
DATAPUMP_EXP_FULL_DATABASE role is required on the source database if the
NETWORK_LINK parameter is used for a full import.
Using the Transportable Option During Full Mode Imports
Network-based full transportable imports require use of the
File-based full transportable imports only require use of the
datafile_name parameter. Data Pump Import infers the presence of the
There are several requirements when performing a full transportable import:
NETWORK_LINK parameter must also be specified or the dump file set being imported must have been created using the transportable option during export.
If you are using a network link, then the database specified on the
NETWORK_LINK parameter must be Oracle Database 11g release 2 (184.108.40.206) or later, and the Data Pump
VERSION parameter must be set to at least 12. (In a non-network import,
VERSION=12 is implicitly determined from the dump file.)
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 import of encrypted tablespaces is not supported in network mode or dump file mode if the source and target platforms do not have the same endianess.
When transporting a database over the network using full transportable import, 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 import, 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.