Specifies that you want to perform a full database import.
Syntax and Description
A value of
FULL=YES indicates that all data and metadata from the source is imported. The source can be a dump file set for a file-based import or it can be another database, specified with the
NETWORK_LINK parameter, for a network import.
If you are importing from a file and do not have the
DATAPUMP_IMP_FULL_DATABASE role, then only schemas that map to your own schema are imported.
NETWORK_LINK parameter is used and the user executing the import job has the
DATAPUMP_IMP_FULL_DATABASE role on the target database, then that user must also have the
DATAPUMP_EXP_FULL_DATABASE role on the source database.
Filtering can restrict what is imported using this import mode (see "Filtering During Import Operations").
FULL is the default mode, and does not need to be specified on the command line when you are performing a file-based import, but if you are performing a network-based full import then you must specify
FULL=Y on the command line.
You can use the transportable option during a full-mode import to perform a full transportable import. See "Using the Transportable Option During Full Mode Imports".
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.
Full imports performed over a network link require that you set
VERSION=12 if the target is Oracle Database 12c Release 1 (18.104.22.168) or later and the source is Oracle Database 11g Release 2 (22.214.171.124) or later.
The following is an example of using the
FULL parameter. You can create the
expfull.dmp dump file used in this example by running the example provided for the Export
FULL parameter. See "FULL".
> impdp hr DUMPFILE=dpump_dir1:expfull.dmp FULL=YES LOGFILE=dpump_dir2:full_imp.log
This example imports everything from the
expfull.dmp dump file. In this example, a
DIRECTORY parameter is not provided. Therefore, a directory object must be provided on both the
DUMPFILE parameter and the
LOGFILE parameter. The directory objects can be different, as shown in this example.