My Oracle Support Banner

Known Issues At Data Pump Import When Using NETWORK_LINK, REMAP_SCHEMA and REMAP_TABLE Parameters (Doc ID 2132017.1)

Last updated on FEBRUARY 26, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 to 12.1.0.1 [Release 11.2 to 12.1]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

NOTE: In the document content below, the user information and data used in the examples represents fictitious data. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Symptoms

In some particular cases of usage of REMAP_TABLE for a table or partition together with NETWORK_LINK and REMAP_SCHEMA data are not imported or are imported in a wrong table.

Case 1: Importing a table through database link into a different schema with a different name using a syntax in which the source table name is qualified by schema name in REMAP_TABLE (TABLES=t1.tab REMAP_SCHEMA=t1:t2 REMAP_TABLE=t1.tab:tab_new) 

1.1. If the table does not exist in target schema, errors are raised but table is created with no rows.

For example:

In source database:

Changes

 

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.