My Oracle Support Banner

DataPump Export Fails with ORA-31623 and ORA-7445 [nszgclient] (Doc ID 2094141.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.3 [Release 10.1 to 11.2]
Information in this document applies to any platform.

Symptoms

Data Pump Export fails with the following errors:

$ expdp USER@DB DIRECTORY=my_dir DUMPFILE=expdp_f.dmp LOGFILE=expdp_f.log FULL=y

Export: Release 11.2.0.2.0 - Production on Mon November 30 15:01:37 2015

Copyright (c) 1982, 2009 Oracle and / or its affiliates. All rights reserved.
Password:
Registered at: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

UDE-31623: operation generated ORACLE error 31623
ORA-31623: a job is not attached to this session via the specified handle
ORA-06512: in "SYS.DBMS_DATAPUMP", line 3326
ORA-06512: in "SYS.DBMS_DATAPUMP", line 4551
ORA-06512: at line 1


Above errors are seen while running DataPump EXPDP with an user other than SYSTEM or 'AS SYSDBA'.
The user has all privileges, roles ,rights as per below note but the DataPump EXPDP still gives above errors.
<Note 351598.1> - Export/Import Data Pump: The Minimum Requirements to Use Export Data Pump and Import Data Pump (System Privileges)

NOTE:
EXPDP works if you use SYSTEM or AS SYSDBA


Following below note does not solve the issue.
<Note 1907256.1> - How to resolve the Data Pump error ORA-31623 (a job is not attached to this session via the specified handle) ?

As there are no errors shown in the alert log around the time of the Data Pump EXPDP, next steps are used to enable tracing for further investigation:

  1. Before restarting the expdp check if there are orphan Data Pump jobs left in database and remove them according to
    <Note 336014.1> - How To Cleanup Orphaned DataPump Jobs In DBA_DATAPUMP_JOBS ?

  2. Enable event:
    SQL> alter system set events='31623 trace name errorstack level 3';
      

  3. Run the expdp
    $ expdp USER@DB DIRECTORY=my_dir DUMPFILE=expdp_f.dmp LOGFILE=expdp_f.log
      

  4. Disable the event
    SQL> alter system set events='31623 trace name errorstack off';
      

  5. Locate the trace file
    SQL> show parameter diagnostic_dest
      
    Find the trace file under <DIAGNOSTIC_DEST>/diag/rdbms/<db_name>/<instance_name>/trace (for uploading/reviewing).


The generated trace file shows information like:

ORA-07445: exception encountered: core dump [nszgclient()]

dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x3, level=3, mask=0x0)

----- Current SQL Statement for this session (sql_id=68jt6115qmhf7) -----
INSERT INTO TRACK_DETAIL (ID, TRACK_TIME, DETAIL) VALUES (TRACK_SEQ.NEXTVAL, SYSTIMESTAMP, :B1 )

----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0x25cbe7ba0 5 procedure USER.TRACK
0x259733a00 15 anonymous block
0x25d760d58 14205 package body SYS.KUPM$MCP
0x25d760d58 7140 package body SYS.KUPM$MCP
0x25d760d58 1415 package body SYS.KUPM$MCP
0x25d760d58 1101 package body SYS.KUPM$MCP
0x25d760d58 869 package body SYS.KUPM$MCP
0x259a1cbb0 2 anonymous block

----- Call Stack -----

... nszgclient kziaguenv kzctxEUsrEnv kzctxAppCtxValGet evactx evaopn2 qesltcFastRowOperandsEvaluateSingle qerltcSingleRowLoad qerltcFetch insexe opiexe opipls opiodr rpidrus skgmstack rpiswu2 rpidrv psddr0 psdnal pevm_EXECC pfrinstr_EXECC pfrrun_no_tool pfrrun plsql_run peicnt kkxexe opiexe ...

 

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