Database Reference
In-Depth Information
Table 8-4.
(
continued
)
Original imp Parameter
Similar Data Pump impdp Parameter
FEEDBACK
STATUS
in client output
FILE
Database directory object and
DUMPFILE
FILESIZE
N/A
FROMUSER
REMAP_SCHEMA
GRANTS
EXCLUDE=OBJECT_GRANT
IGNORE
TABLE_EXISTS_ACTION
, with
APPEND
,
REPLACE
,
SKIP
, or
TRUNCATE
INDEXES
EXCLUDE=INDEXES
INDEXFILE
SQLFILE
LOG
Database directory object and
LOGFILE
RECORDLENGTH
N/A
RESUMABLE
N/A; this functionality is automatically provided.
RESUMABLE_NAME
N/A
RESUMABLE_TIMEOUT
N/A
ROWS=N
CONTENT
, with
METADATA_ONLY
or
ALL
SHOW
SQLFILE
STATISTICS
N/A
STREAMS_CONFIGURATION
N/A
STREAMS_INSTANTIATION
N/A
TABLESPACES
TRANSPORT_TABLESPACES
TOID_NOVALIDATE
N/A
TOUSER
REMAP_SCHEMA
TRANSPORT_TABLESPACE
TRANSPORT_TABLESPACES
TTS_OWNERS
N/A
VOLSIZE
N/A; Data Pump doesn't support tape devices.
Summary
Data Pump is an extremely powerful and feature-rich tool. If you haven't used Data Pump much, then I recommend
that you take some time to reread this chapter and work through the examples. This tool greatly simplifies tasks such
as moving users and data from one environment to another. You can export and import subsets of users, filter and
remap data via SQL and PL/SQL, rename users and tablespaces, compress, encrypt, and parallelize, all with one
command. It really is that powerful.
DBAs sometimes stick with the old
exp
/
imp
utilities because that's what they're familiar with (I'm occasionally
guilty of this). If you're running Oracle 11g Release 2, you can use the old
exp
/
imp
parameters and options directly
from the command line. Data Pump translates these parameters on the fly to Data Pump-specific syntax. This feature
nicely facilitates the migration from the old to the new. For reference, I've also provided a mapping of the old
exp
/
imp
syntax and how it relates to Data Pump commands.
