Thanks everyone for your ideas but ...
OK so this was fixed by Oracle! . I did a drop user cascade while the
impdp was running. This - somehow resulted in objects being owned by a non
existent user. I had to run some 'secret' code to modify the data
dictionary. So be careful out there!
On 18 April 2016 at 17:25, Chris Taylor <christopherdtaylor1994@xxxxxxxxx>
wrote:
Did you check DBA_DATAPUMP_JOBS to see if it's still listed in there with
an incorrect status? It may be marked STOPPED or something (can't remember
the statuses off the top of my head).
If it's listed there with a failed status or something, you'll have to
clean it out.
Check the below note on how to cleanup orphaned jobs if you have any.
How to Cleanup Orphaned DataPump Jobs In DBA_DATAPUMP_JOBS [ID 336014.1]
Chris
On Mon, Apr 18, 2016 at 11:01 AM, Howard Latham <howard.latham@xxxxxxxxx>
wrote:
Version 11.2.04
Linux Redhat Ent 4
After a failed impdp and then I dropped a user to retry import impdp
will not work.
I've logged it with Oracle support but so far nothing.
Its not the streams size that comes up with google . OS said it might be
a data dictionary inconsistency.
Import: Release 11.2.0.1.0 - Production on Mon Apr 18 16:58:04 2016
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights
reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 -
64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options
UDI-31623: operation generated ORACLE error 31623
ORA-31623: a job is not attached to this session via the specified handle
ORA-06512: at "SYS.DBMS_DATAPUMP", line 3263
ORA-06512: at "SYS.DBMS_DATAPUMP", line 4488
ORA-06512: at line 1
Any ideas? Anyone?
--
Howard A. Latham
