My Oracle Support Banner

DataPump Fails With ORA-39325 When Importing Into A Newly Created Instance. (Doc ID 3039747.1)

Last updated on AUGUST 06, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A to N/A
Gen 2 Exadata Cloud at Customer - Version N/A to N/A [Release All Releases]
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A to N/A [Release N/A]
Information in this document applies to any platform.

Symptoms

Create a new instance, then import schemas into this new instance via DataPump, but ORA-39325 occurs, re-import completes without the error.

Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/SEQUENCE
Processing object type DATABASE_EXPORT/SCHEMA/SYNONYM
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/TYPE_SPEC
Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE
ORA-39325: TABLE_EXISTS_ACTION cannot be applied to "<Schema_name>"."<Table_name>".

The error can only reproduce when import into a new instance, and the "<Schema_name>"."<Table_name>" is varying every time.

In addition, there is not the same name's object in the new instance.

Changes

None.

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


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