My Oracle Support Banner

Datapump Export Fails With ORA-39126: Worker unexpected fatal error in KUPW$WORKER.GATHER_PARSE_ITEMS (Doc ID 2067271.1)

Last updated on JANUARY 01, 2021

Applies to:

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

Symptoms

1.  The Datapump export of 12.1.0.2  fails with the following errors when exporting a Java object:

ORA-39126: Worker unexpected fatal error in KUPW$WORKER.GATHER_PARSE_ITEMS [JAVA_CLASS:"SYSTEM"."<JAVA_CLASS>"]

Remarks: 

The issue reproduces with Pluggable non-Pluggable and standalone databases

2.  Steps needed to reproduce the issue:

a) Load the SVL1004C.jar into the system schema of the 12c Database via the following command on the Linux prompt:

% loadjava -u system/@<SERVICE_NAME> -r -v -f -genmissing -jarsasdbobjects -prependjarnames <CLASS_NAME>.jar -fileout<LOG_NAME>.log

Remarks:

The object name in user_objects is not the object_name used in dbms_metadata.get_ddl.  Use the dbms_java.longname function to get the correct object

In user objects the object type is 'JAVA CLASS', so with a space in between, the object name to be used in dbms_metadata.getddl is 'JAVA_CLASS', so with the underscore instead of the space!

b) Create a database directory for Datapump export in SQL*Plus:

SQL> create directory exp as '<PATH>';

c) On the operating system prompt start the export:

% expdp system/<PASSWORD> DIRECTORY=<DIRECTORY_NAME> DUMPFILE=<DUMP_NAME>.dmp

This last step will fail with messages like shown below:

Export: Release 12.1.0.2.0 - Production on Mon Apr 20 15:44:34 2015
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
Starting "SYSTEM"."SYS_EXPORT_SCHEMA_01": system/********@<SERVICE_NAME> DIRECTORY=<DIRECTORY_NAME> DUMPFILE=<DUMP_NAME>.dmp
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 19.25 MB
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/LIBRARY/LIBRARY
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/JAVA_CLASS/JAVA_CLASS
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.GATHER_PARSE_ITEMS [JAVA_CLASS:"SYSTEM"."<JAVA_CLASS>"]
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 11259

----- PL/SQL Call Stack -----
 object line object
 handle number name
0x7e7dffc0 27116 package body SYS.KUPW$WORKER
0x7e7dffc0 11286 package body SYS.KUPW$WORKER
0x7e7dffc0 15779 package body SYS.KUPW$WORKER
0x7e7dffc0 9645 package body SYS.KUPW$WORKER
0x7e7dffc0 13381 package body SYS.KUPW$WORKER
0x7e7dffc0 3173 package body SYS.KUPW$WORKER
0x7e7dffc0 12035 package body SYS.KUPW$WORKER
0x7e7dffc0 2081 package body SYS.KUPW$WORKER
0x85513778 2 anonymous block

 

Changes

The 11g database is upgraded to 12c.  The issue can reproduce even with a freshly created 12c database

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
References


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