Syntax and Description
DUMPFILE=[directory_object:]file_name [, ...]
directory_object is optional if one has already been established by the
DIRECTORY parameter. If you do supply a value here, then it must be a directory object that already exists and that you have access to. A database directory object that is specified as part of the
DUMPFILE parameter overrides a value specified by the
file_name is the name of a file in the dump file set. The file names can also be templates that contain the substitution variable,
%U is used, then Import examines each file that matches the template (until no match is found) to locate all files that are part of the dump file set. The
%U expands to a 2-digit incrementing integer starting with 01.
Sufficient information is contained within the files for Import to locate the entire set, provided the file specifications in the
DUMPFILE parameter encompass the entire set. The files are not required to have the same names, locations, or order that they had at export time.
Dump files created on Oracle Database 11g releases with the Data Pump parameter
VERSION=12 can only be imported on Oracle Database 12c Release 1 (12.1) and later.
The following is an example of using the Import
DUMPFILE parameter. You can create the dump files used in this example by running the example provided for the Export
DUMPFILE parameter. See "DUMPFILE".
> impdp hr DIRECTORY=dpump_dir1 DUMPFILE=dpump_dir2:exp1.dmp, exp2%U.dmp
Because a directory object (
dpump_dir2) is specified for the
exp1.dmp dump file, the import job will look there for the file. It will also look in
dpump_dir1 for dump files of the form
.dmp. The log file will be written to