My Oracle Support Banner

DataPump Import Cannot Remap Table Name For Partitioned Table (Doc ID 1276088.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Server - Enterprise Edition - Version: and later   [Release: 11.2 and later ]
Information in this document applies to any platform.


You have written a code that tries to do a network DataPump import using the DBMS_DATAPUMP API and nted to transfer thae data from a range/list partitioned table A on the remote site to a table B on the local site. Table B has the same DDL but is not partitioned and will be used to partition exchange load table A on the local site. Table A has many bitmap indexes on it, so you do not want to pump from table A on the remote site to table A on the local site and have to do index maintenance.

Because table A exists on each site, you need to pump from remote to local with table name remapping. However, you have not been able to get the table to be renamed on the local site. You invoked the dbms_datapump.metadata_remap procedure and tell it to remap the table name, but it basically ignores and imports the table with the original name. A non-partitioned table will remap,
but not to a partitioned table.


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

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