Ignore and fromuser/touser functions of Oracleimpdp

When impdp is used, we can find that many Parameter options are different from imp. For example, fromuser and touser parameters cannot be found, ignore parameters, indexes and other parameters cannot be found.

When impdp is used, we can find that many Parameter options are different from imp. For example, fromuser and touser parameters cannot be found, ignore parameters, indexes and other parameters cannot be found.

When you use impdp, you will find that many Parameter options are different from imp. For example, you cannot find the fromuser and touser parameters, you cannot find the ignore parameters, and parameters such as indexes no longer exist.

Of course, these functions are still available and more powerful. impdp has many new substitution parameters.
The following three parameters greatly enhance user conversion and table space conversion operations:
REMAP_DATAFILE Redefine datafile references in all DDL statements.
REMAP_SCHEMA Objects from one schema are loaded into another schema.
REMAP_TABLESPACE Tablespace object are remapped to another tablespace.

REMAP_SCHEMA defines User Switching in the format:
Remap_schema = old_schema_name: new_schema_name

REMAP_TABLESPACE can define different tablespaces of the switching object. The format is as follows:
Rempa_tablesapce = old_tablespace_name: new_tablespace_name

Previously, an error similar to IGNORE can be ignored. You can use the CONTENT parameter:
CONTENT Specifies data to load where the valid keywords are:
(ALL), DATA_ONLY, and METADATA_ONLY.

If the data structure already exists, you can specify CONTENT = DATA_ONLY to import only data.

You can use the EXCLUDE parameter to EXCLUDE indexes:
EXCLUDE Exclude specific object types, e.g. EXCLUDE = TABLE: EMP.

If you ignore indexes during IMPDP import, you can use the following methods: EXCLUDE = constraint exclude = INDEX.

If the following error occurs during import, you need to adjust the REMAP_SCHEMA parameter:
ORA-39146: schema "SMS_MT" does not exist

If the following error occurs, you need to set the REMAP_TABLESPACE parameter:
ORA-00959: tablespace 'sms _ mt' does not exist

The parameters used today are:
Impdp sms4/sms4 dumpfile = 08.dmp directory = impdp TABLES = smsmg REMAP_SCHEMA = SMS: SMS4 REMAP_TABLESPACE = SMS_MT: sms content = DATA_ONLY PARALLEL = 8 EXCLUDE = constraint exclude = INDEX

Record it for reference.