Impdp With REMAP_SCHEMA And Nonexistent Source Schema Might Import Unwanted Data
Last updated on MARCH 09, 2018
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2]
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 220.127.116.11 [Release 10.1 to 11.2]
Information in this document applies to any platform.
Impdp With REMAP_SCHEMA And Inexistant 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms