Impdp With REMAP_SCHEMA And Nonexistent Source Schema Might Import Unwanted Data
(Doc ID 1121345.1)
Last updated on MAY 14, 2021
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 11.2]
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 126.96.36.199 [Release 10.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Impdp With REMAP_SCHEMA and non-existent source schema might import unwanted data.
Suppose you have a dump file containing a table called TEST from schema A and you would like to import table A.TEST into schema B.
For this, you specify 'REMAP_SCHEMA=A:B' as parameter when calling Datapump Import.
In this case, all is fine.
However, in case you enter a typo or specify a parameter like 'REMAP_SCHEMA=C:B' and source schema C does not exist in the dump file, than table A.TEST is still imported but in schema A.
Number of Customers are using the 'REMAP_SCHEMA' parameter to move objects from one schema to another and would prefer the Import to stop in case of mistakes/typos in the 'REMAP_SCHEMA' parameters.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document