All Data Pump Export and
Import processing is done on the server instead of the client, which requires directory objects on
the source and target databases.
Here are a few of the other enhancements and features over the original exp and imp utilities:
The job that exports or imports can control the number of parallel threads used for the job.
A Data Pump job can be restarted if the job fails or is stopped.
Export and import are supported over the network without using dump file sets.
The ability is provided to attach and detach from a running job by a client process.
Space can be estimated, without actually performing the export.
You can specify the database version of objects to be exported or imported.
Support is included for fine-grained filtering of metadata as well as data filtering on a
table-by-table basis.
We will also cover transportable tablespaces using the features of Data Pump and the package
DBMS_FILE_TRANSFER to create and move a tablespace dump set to another database.
?–
?–
?–
?–
?–
?–
?–
?–
?–
?–
?–
?–
592 Oracle Database 11g DBA Handbook
Data Pump Export
Data Pump Export, or just Export, unloads data and metadata into a set of operating system files
called a dump file set. The dump file set is only readable by Data Pump Import. The dump file set
consists of one or more disk files containing the metadata, data, and control information, and it??™s
written in a proprietary binary format.
Pages:
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872