Default: NO
Purpose
Syntax and Description
FULL=[YES | NO]
FULL=YES
indicates that all data and metadata are to be exported. To perform a full export, you must have the DATAPUMP_EXP_FULL_DATABASE
role.
Filtering can restrict what is exported using this export mode. See "Filtering During Export Operations".
You can perform a full mode export using the transportable option (TRANSPORTABLE=ALWAYS
). This is referred to as a full transportable export, which exports all objects and data necessary to create a complete copy of the database. See "Using the Transportable Option During Full Mode Exports".
Be aware that when you later import a dump file that was created by a full-mode export, the import operation attempts to copy the password for the SYS
account from the source database. This sometimes fails (for example, if the password is in a shared password file). If it does fail, then after the import completes, you must set the password for the SYS
account at the target database to a password of your choice.
Restrictions
To use the FULL
parameter in conjunction with TRANSPORTABLE
(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.
A full export does not, by default, export system schemas that contain Oracle-managed data and metadata. Examples of system schemas that are not exported by default include SYS
, ORDSYS
, and MDSYS
.
Grants on objects owned by the SYS
schema are never exported.
A full export operation exports objects from only one database edition; by default it exports the current edition but you can use the Export SOURCE_EDITION
parameter to specify a different edition.
If you are exporting data that is protected by a realm, then you must have authorization for that realm.
The Automatic Workload Repository (AWR) is not moved in a full database export and import operation. (See Oracle Database Performance Tuning Guide for information about using Data Pump to move AWR snapshots.)
The XDB repository is not moved in a full database export and import operation. User created XML schemas are moved.
Example
The following is an example of using the FULL
parameter. The dump file, expfull.dmp
is written to the dpump_dir2
directory.
> expdp hr DIRECTORY=dpump_dir2 DUMPFILE=expfull.dmp FULL=YES NOLOGFILE=YES
Oracle Database Administrator's Guide for a detailed example of how to perform a full transportable export
Oracle Database Vault Administrator's Guide for information about configuring realms