Datapump import with REMAP_TABLE clause giving wrong results
(Doc ID 1544270.1)
Last updated on MAY 17, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 12.1.0.1 [Release 10.2 to 12.1]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 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.
Symptoms
When trying to remap tables during datapump import with table_exists_action=truncate as follows:
- t1 -> t2
- t2 -> t3
Where t1 and t2 are export tables from the source database and the destination tables t2 and t3 are existing tables in the destination database
Table t2 is empty.
The remap imported the data from both t1 and t2 into t3!
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 |
| Changes |
| Cause |
| Solution |
| References |