My Oracle Support Banner

Datapump Import Fails with Segmentation Fault When Using Multiple Modes (Doc ID 2388296.1)

Last updated on JANUARY 29, 2020

Applies to:

Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.


Attempting to run datapump import with multiple modes defined results in a segmentation fault and a core dumped. For example, this syntax uses the schemas and tables modes and fails.

$ impdp schemas=<schama_name> tables=<table_name> logfile=imp.log TABLE_EXISTS_ACTION=REPLACE
Import: Release - Production on Tue Apr 17 10:16:06 2018

Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

Username: <name>

Connected to: Oracle Database 11g Enterprise Edition Release - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, Oracle Label Security,
OLAP, Data Mining, Oracle Database Vault and Real Application Testing optio
Segmentation fault (core dumped)

However, running it with only one mode defined succeeds.

This problem can also occur when these modes are set in an datapump parameter file.



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.