Traditional Export (EXP) Core Dumped On Hash Partitioned Table (Doc ID 331793.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.1.0.4 - Release: 10.1 to 10.1
Information in this document applies to any platform.

Symptoms

Export on Hash Partitioned Table core dumps, like the next test demonstrates:

connect test/passwd
create table emp
(
   emp_id  number(5),
   empname varchar2(20)
)
partition by hash (emp_id)
partitions 4
store in (part1, part2, part3, part4);

create unique index empindx on emp (emp_id)
global partition by hash (emp_id)
(
   partition p_indx1 tablespace part1,
   partition p_indx2 tablespace part2,
   partition p_indx3 tablespace part3,
   partition p_indx4 tablespace part4
);

#> exp test/passwd file=emp.dmp tables=emp

Export: Release 10.1.0.2.0 - Production on Sat Aug 20 20:37:48 2005
Copyright (c) 1982, 2004, Oracle.  All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - 64bit
Production
With the Partitioning, OLAP and Data Mining Scoring Engine options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses WE8MSWIN1252 character set (possible charset conversion)
About to export specified tables via Conventional Path ...
. . exporting table                            EMP
. . exporting partition                        SYS_P25          0 rows exported
. . exporting partition                        SYS_P26          0 rows exported
. . exporting partition                        SYS_P27          0 rows exported
. . exporting partition                        SYS_P28          0 rows exportedS
Segmentation Fault (core dumped)

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