datapump ORA-44002

Datapump Export Fails ORA-39006 ORA-39065 ORA-44002 [ID 435344.1]

Applies to:

Oracle Server - Enterprise Edition - Version 10.1.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 12-Jul-2012***

Symptoms

While performing a datapump export with a non privileged user the following errors are occuring :

[oracle@ro-rac4 dp]$ expdp scott/tiger directory=mydatapump schemas=scott logfile=scott.log dumpfile=scott.dmp

Export: Release 10.2.0.1.0 - Production on Friday, 08 June, 2007 10:18:13

Copyright (c) 2003, 2005, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options
ORA-39006: internal error
ORA-39065: unexpected master process exception in DISPATCH
ORA-44002: invalid object name
ORA-06512: at "SYS.KUPF$FILE", line 4372
ORA-06512: at line 1

ORA-39097: Data Pump job encountered unexpected error -44002

The trace file produced by the 44002 event shows the following errorstack :

ORA-44002: invalid object name
Current SQL statement for this session:
BEGIN SYS.KUPF$FILE.INIT_CB(:jn,:jo,:hs,:wid,:op,:bs,:ds,:ms,:poif,:poim, :mton, :dbg, :dbgTmStamp, :dbgIdent, :dbgSeqIO, :inst, :guid, :mdCmp, :tdCmp, :jobVersion); END;
----- PL/SQL Call Stack -----
object line object
handle number name
0x3db1122c 264 package body SYS.DBMS_ASSERT
0x3a64db64 835 package body SYS.KUPF$FILE
0x3a64db64 4301 package body SYS.KUPF$FILE
0x3d799ee0 1 anonymous block
0x3a7bb1c8 486 package body SYS.KUPF$FILE_INT
0x3a64db64 4164 package body SYS.KUPF$FILE
0x3bffd938 1811 package body SYS.KUPM$MCP
0x3bffd938 1060 package body SYS.KUPM$MCP
0x3bffd938 675 package body SYS.KUPM$MCP
0x3a6c7170 2 anonymous block

Cause

The error occurs because the SYS schema already contains a procedure with the name SCOTT. The same error would occur  if the SYS schema would have a  function or sequence named SCOTT. The error does not occur if there is a table, index or directory named SCOTT.

Note that you can easily reproduce the issue after creating the directory object, granting read and write to scott and simply defining 'create sequence scott;' in the sys schema.

Solution

Rename any procedure, function or sequence having the same name as the user executing the datapump export.