Databases Reference
In-Depth Information
In many instances, there isn't a one-to-one mapping. Often, Data Pump automatically provides features that used
to require a parameter in the legacy utilities. For example, whereas you used to have to specify
DIRECT=Y
to get a direct
path export, Data Pump automatically uses direct path whenever possible.
Data Pump Mapping to the imp Utility
As with Data Pump export, Data Pump import often doesn't have a one-to-one mapping of the legacy utility
parameter. Data Pump import automatically provides many features of the old
imp
utility. For example,
COMMIT=Y
isn't
required because Data Pump import automatically commits after each table is imported. Table
13-4
describes how
the legacy import parameters map to Data Pump import.
Table 13-4.
Mapping of Old Import Parameters to Data Pump
Original imp Parameter
Similar Data Pump impdp Parameter
BUFFER
N/A
CHARSET
N/A
COMMIT
N/A; Data Pump import automatically commits after each table is exported.
COMPILE
N/A; Data Pump import compiles procedures after they're created.
CONSTRAINTS
EXCLUDE=CONSTRAINT
DATAFILES
TRANSPORT_DATAFILES
DESTROY
REUSE_DATAFILES=y
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
(
continued
)
