|
BUFFER
|
This parameter is ignored.
|
|
CHARSET
|
This parameter was desupported several releases ago and should no longer be used. It will cause the Data Pump Import operation to abort.
|
|
COMMIT
|
This parameter is ignored. Data Pump Import automatically performs a commit after each table is processed.
|
|
COMPILE
|
This parameter is ignored. Data Pump Import compiles procedures after they are created. A recompile can be executed if necessary for dependency reasons.
|
|
CONSTRAINTS
|
If original Import used CONSTRAINTS=n, then Data Pump Import uses the EXCLUDE=CONSTRAINT parameter.
If original Import used CONSTRAINTS=y, then the parameter is ignored and does not need to be remapped because that is the Data Pump Import default behavior.
|
|
DATAFILES
|
The Data Pump Import TRANSPORT_DATAFILES parameter is used.
|
|
DESTROY
|
If original Import used DESTROY=y, then Data Pump Import uses the REUSE_DATAFILES=y parameter.
If original Import used DESTROY=n, then the parameter is ignored and does not need to be remapped because that is the Data Pump Import default behavior.
|
|
FEEDBACK
|
The Data Pump Import STATUS=30 command is used. Note that this is not a direct mapping because the STATUS command returns the status of the import job, as well as the rows being processed.
In original Import, feedback was given after a certain number of rows, as specified with the FEEDBACK command. In Data Pump Import, the status is given every so many seconds, as specified by STATUS.
|
|
FILE
|
Data Pump Import attempts to determine the path that was specified or defaulted to for the FILE parameter, and also to determine whether a directory object exists to which the schema has read and write access.
See "Management of File Locations in Data Pump Legacy Mode" for more information about how Data Pump handles the original Import FILE parameter.
|
|
FILESIZE
|
This parameter is ignored because the information is already contained in the Data Pump dump file set.
|
|
FROMUSER
|
The Data Pump Import SCHEMAS parameter is used. If FROMUSER was used without TOUSER also being used, then import schemas that have the IMP_FULL_DATABASE role cause Data Pump Import to attempt to create the schema and then import that schema's objects. Import schemas that do not have the IMP_FULL_DATABASE role can only import their own schema from the dump file set.
|
|
GRANTS
|
If original Import used GRANTS=n, then Data Pump Import uses the EXCLUDE=OBJECT_GRANT parameter.
If original Import used GRANTS=y, then the parameter is ignored and does not need to be remapped because that is the Data Pump Import default behavior.
|
|
IGNORE
|
If original Import used IGNORE=y, then Data Pump Import uses the TABLE_EXISTS_ACTION=APPEND parameter. This causes the processing of table data to continue.
If original Import used IGNORE=n, then the parameter is ignored and does not need to be remapped because that is the Data Pump Import default behavior.
|
|
INDEXES
|
If original Import used INDEXES=n, then Data Pump Import uses the EXCLUDE=INDEX parameter.
If original Import used INDEXES=y, then the parameter is ignored and does not need to be remapped because that is the Data Pump Import default behavior.
|
|
INDEXFILE
|
The Data Pump Import SQLFILE={directory-object:}filename and INCLUDE=INDEX parameters are used.
The same method and attempts made when looking for a directory object described for the FILE parameter also take place for the INDEXFILE parameter.
If no directory object was specified on the original Import, then Data Pump Import uses the directory object specified with the DIRECTORY parameter.
|
|
LOG
|
Data Pump Import attempts to determine the path that was specified or defaulted to for the LOG parameter, and also to determine whether a directory object exists to which the schema has read and write access.
See "Management of File Locations in Data Pump Legacy Mode" for more information about how Data Pump handles the original Import LOG parameter.
The contents of the log file will be those of a Data Pump Import operation. See "Log Files" for information about log file location and content.
|
|
RECORDLENGTH
|
This parameter is ignored because Data Pump handles issues about record length internally.
|
|
RESUMABLE
|
This parameter is ignored because this functionality is automatically provided for users who have been granted the IMP_FULL_DATABASE role.
|
|
RESUMABLE_NAME
|
This parameter is ignored because this functionality is automatically provided for users who have been granted the IMP_FULL_DATABASE role.
|
|
RESUMABLE_TIMEOUT
|
This parameter is ignored because this functionality is automatically provided for users who have been granted the IMP_FULL_DATABASE role.
|
|
ROWS=N
|
If original Import used ROWS=n, then Data Pump Import uses the CONTENT=METADATA_ONLY parameter.
If original Import used ROWS=y, then Data Pump Import uses the CONTENT=ALL parameter.
|
|
SHOW
|
If SHOW=y is specified, then the Data Pump Import SQLFILE=[directory_object:]file_name parameter is used to write the DDL for the import operation to a file. Only the DDL (not the entire contents of the dump file) is written to the specified file. (Note that the output is not shown on the screen as it was in original Import.)
The name of the file will be the file name specified on the DUMPFILE parameter (or on the original Import FILE parameter, which is remapped to DUMPFILE). If multiple dump file names are listed, then the first file name in the list is used. The file will be located in the directory object location specified on the DIRECTORY parameter or the directory object included on the DUMPFILE parameter. (Directory objects specified on the DUMPFILE parameter take precedence.)
|
|
STATISTICS
|
This parameter is ignored because statistics are always saved for tables as part of a Data Pump Import operation.
|
|
STREAMS_CONFIGURATION
|
This parameter is ignored because Data Pump Import automatically determines it; it does not need to be specified.
|
|
STREAMS_INSTANTIATION
|
This parameter is ignored because Data Pump Import automatically determines it; it does not need to be specified
|
|
TABLESPACES
|
If original Import also specified TRANSPORT_TABLESPACE=n (the default), then Data Pump Import ignores the TABLESPACES parameter.
If original Import also specified TRANSPORT_TABLESPACE=y, then Data Pump Import takes the names supplied for this TABLESPACES parameter and applies them to the Data Pump Import TRANSPORT_TABLESPACES parameter.
|
|
TOID_NOVALIDATE
|
This parameter is ignored. OIDs are no longer used for type validation.
|
|
TOUSER
|
The Data Pump Import REMAP_SCHEMA parameter is used. There may be more objects imported than with original Import. Also, Data Pump Import may create the target schema if it does not already exist.
The FROMUSER parameter must also have been specified in original Import or the operation will fail.
|
|
TRANSPORT_TABLESPACE
|
The TRANSPORT_TABLESPACE parameter is ignored, but if you also specified the DATAFILES parameter, then the import job continues to load the metadata. If the DATAFILES parameter is not specified, then an ORA-39002:invalid operation error message is returned.
|
|
TTS_OWNERS
|
This parameter is ignored because this information is automatically stored in the Data Pump dump file set.
|
|
VOLSIZE
|
When the original Import VOLSIZE parameter is used, it means the location specified for the dump file is a tape device. The Data Pump Import dump file format does not support tape devices. Therefore, this operation terminates with an error.
|