A common technique used with exp/imp was compressing through a Pipe. Apparently this cannot be done with data pump "the ... dumpfile ... is no longer processed in a sequential manner.
Dump files generated by the original export utility (exp) cannot be imported by the new data pump import utility (impdp) and vice-versa.
Data Pump Export (expdp) and Data Pump Import (impdp) are server-based rather than client-based as is the case for the original export (exp) and import (imp). Because of this, dump files, log files, and sql files are accessed relative to the server-based directory paths.
Data Pump requires that directory objects mapped a file system directory be specified in the invocation of the data pump import or export. It for this reason and for convenience that a directory object be created before using the data pump export or import utilities.
For example to create a directory object named expdp_dir located at /u01/backup/exports enter the following sql statement:
Data Pump Export
Full Export Mode
You can invoke the data pump export using a command line. Export
parameters can be specified directly in the command line. A full export
is specified using the FULL parameter. In a full database export, the
entire database is unloaded. This mode requires that you have the
EXP_FULL_DATABASE role.Shown below is an example
$ expdp system/<password> DIRECTORY=exp_dir DUMPFILE=expfull.dmp FULL=y LOGFILE=expfull.og
chema Export Mode
The schema export mode is invoked using the SCHEMAS parameter. If you
have no EXP_FULL_DATABASE role, you can only export your own schema. If
you have EXP_FULL_DATABASE role, you can export several schemas in one
go. Optionally, you can include the system privilege grants as well.
$ expdp hr/hr DIRECTORY=exp_dir DUMPFILE=schema_exp.dmp SCHEMAS=hr,finance
$ expdp hr/hr DIRECTORY=exp_dir DUMPFILE=tables_exp.dmp TABLES=employees,jobs,departments
Full Import Mode The full import mode loads the entire contents of the source (export) dump file to the target database. However, you must have been granted the IMP_FULL_DATABASE role on the target database. The data pump import is invoked using the impdp command in the command line with the FULL parameter specified in the same command line.
$ impdp system/<password> DIRECTORY=exp_dir DUMPFILE=expfull.dmp FULL=y LOGFILE=impfull.og
Schema Import Mode The schema import mode is invoked using the SCHEMAS parameter. Only the contents of the specified schemas are load into the target database. The source dump file can be a full, schema-mode, table, or tablespace mode export files. If you have a IMP_FULL_DATABASE role, you can specify a list of schemas to load into the target database.
$ impdp hr/hr DIRECTORY=exp_dir DUMPFILE=expfull.dmp SCHEMAS=hr
All data pump actions are performed by multiple jobs (server processes not DBMS_JOB jobs).These jobs
are controlled by a master control process which uses Advanced Queuing. At runtime an advanced queue table, named after the job name, is created and used by the master control process.The table is dropped on completion of the data pump job. The job and the advanced queue can be named using the JOB_NAME parameter. Cancelling the client process does not stop the associated data pump job.Issuing "ctrl+c" on the client during a job stops the client output and presents a command prompt. Typing "status" at this prompt allows you to monitor the current job.
$ exp system/password para=emdev.par
$expdp hr DIRECTORY=dpump_dir1 DUMPFILE=hr.dmp CONTENT=METADATA_ONLY