CAUTION: REMAP_SCHEMA And TABLE_EXISTS_ACTION Used With DataPump Import Can be Very Dangerous
(Doc ID 1326843.1)
Last updated on APRIL 05, 2023
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Symptoms
Using REMAP_SCHEMA and TABLE_EXISTS_ACTION together during DataPump import (impdp) is extremely dangerous.
Please find the below test case to understand the issue.
Even with the correct argument in the remap_schema, the table in schema TEST_EXP2 is affected and the object of TEST_EXP1 is now exported to TEST_EXP3.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |