Expdp Segmentation Fault (Core Dumped) for more than 14 Schemas (Doc ID 1389763.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 30-May-2013***

Symptoms

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=test_dump.dmp logfile=test_dump.log schemas= finixr, finixm, finixd, finixds, csmswt, csmswd, csmswg, csmswr, analysisd, analysist, mnsubtab, hecmd, seamd, subpr, scott, webdba

Export: Release 11.2.0.2.0 - Production on Mon Nov 14 20:42:44 2011

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Password:
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:

flounder-ng2{oracle-FISH}: /bin/adb $ORACLE_HOME/bin/expdp core
core file = core -- program ``/oracle/prod/11.2/db1/bin/expdp'' on platform i86pc
SIGSEGV: Segmentation Fault
$c
libc.so.1`_lwp_kill+0xa()
libc.so.1`raise+0x19()
libclntsh.so.11.1`skgesigOSCrash+0x1dd()
libclntsh.so.11.1`kpeDbgSignalHandler+0x7a()
libclntsh.so.11.1`skgesig_sigactionHandler+0x3c2()
libc.so.1`__sighndlr+6()
libc.so.1`call_user_handler+0x252()
libc.so.1`sigacthandler+0xee(b, fffffd7fffdf7a10, fffffd7fffdf76b0)
libclntsh.so.11.1`lxCmpStr+0x18f()
libclntsh.so.11.1`lxoCmpStr+0x15f()
libclntsh.so.11.1`lxsCmpStr+0x7c()
udcCopyCommandLine+0x86d()
udeMain+0x33b8()
0x4053ec()


The relevant functions of the call stack seem to be:

... lxCmpStr lxoCmpStr lxsCmpStr ...


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.:

_lwp_kill skgesigOSCrash kpeDbgSignalHandler skgesig_sigactionHandler sighndlr



Settings for swap and ulimit were checked, but nothing relevant was found.

The alert.log shows no entry referring to the issue.

Changes

None.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms