Expdp Segmentation Fault (Core Dumped) for more than 14 Schemas
(Doc ID 1389763.1)
Last updated on AUGUST 01, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Information in this document applies to any platform.
Expdp fails with Segmentation Fault (core dump), if trying to export more than 14 Schemas like below:
expdp userid=system directory=data_pump_dir dumpfile=<dump_name>.dmp logfile=<log_name>.log schemas=<schema1>,<schema2>,<schema3>,<schema4>,<schema5>,<schema6>,<schema7>,<schema8>,<schema9>,<schema10>,<schema11>,<schema12>,<schema13>,<schema14>,...
Export: Release 184.108.40.206.0 - Production on Mon Nov 14 20:42:44 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Segmentation Fault (core dumped)
If the last three schema names are removed, the export works fine.
Extracting the stack trace from the core dump with adb, we get:
core file = core -- program ``<$ORACLE_HOME>/bin/expdp'' on platform i86pc
SIGSEGV: Segmentation Fault
libc.so.1`sigacthandler+0xee(b, fffffd7fffdf7a10, fffffd7fffdf76b0)
The relevant functions of the call stack seem to be:
Most of the call stack above that is Oracle generic code for catching the segmentation fault signal and trying to handle that cleanly, i.e.:
Settings for swap and ulimit were checked, but nothing relevant was found.
The alert.log shows no entry referring to the issue.
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