Datapump import with REMAP_TABLE clause giving wrong results (Doc ID 1544270.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 12.1.0.1.0 [Release 10.2 to 12.1]
Information in this document applies to any platform.

Symptoms

When trying to remap tables during datapump import with table_exists_action=truncate as follows:

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

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