DataPump Import (IMPDP) Inserts Data Twice Using PARTITION_OPTIONS=MERGE and TABLE_EXISTS_ACTION=SKIP
(Doc ID 2525896.1)
Last updated on APRIL 17, 2019
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 18]
Oracle Cloud Infrastructure - Database Service - Version N/A to N/A [Release 1.0]
Autonomous Data Warehouse Cloud - Version N/A to N/A
Autonomous Transaction Processing - Version NA to NA [Release NA]
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 from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product.
Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
If table gets loaded when target table pre-exists and PARTITION_OPTIONS=MERGE and TABLE_EXISTS_ACTION=SKIP is specified in par file or command line, duplicate rows are created.
Although IMPDP honors the skip request, the table data is imported again when PARTITION_OPTIONS=MERGE is specified.
Simple test case scenario :
+++ Create simple table, insert some data and export the table.
+++ Import the table using TABLE_EXISTS_ACTION=SKIP and PARTITION_OPTIONS=MERGE = One row is loaded
+++ Import the table again using TABLE_EXISTS_ACTION=SKIP and PARTITION_OPTIONS=MERGE = The rows is loaded again
+++ Duplicate rows are created if we import again from the same set of data.
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