Take a look in dba_datapump_jobs. The job may still be in there and even if it's not really functioning you can't start a new job by the same name till you clear this one. Sometimes connecting with impdp/expdp and attaching to the job will allow you to kill it, but sometimes it's already dead, just the master table, which has the same name as the job, hasn't been deleted yet. Simply drop that table and it should clear up nicely. Dick Goulet Senior Oracle DBA/NA Team Lead PAREXEL International ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of John Dunn Sent: Friday, December 04, 2009 6:32 AM To: oracle-l digest users Subject: datapump errors I have run datapump on a regular basis on the same schema but now get the errors below: There have been no database upgrades or anything Any ideas? Connected to: Oracle Database 10g Release 10.2.0.1.0 - 64bit Production ORA-31626: job does not exist ORA-31637: cannot create job SYS_SQL_FILE_FULL_01 for user PRODUCER ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95 ORA-06512: at "SYS.KUPV$FT_INT", line 600 ORA-39080: failed to create queues "KUPC$C_1_20091204112459" and "KUPC$S_1_20091 204112459" for Data Pump job ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95 ORA-06512: at "SYS.KUPC$QUE_INT", line 1555 ORA-04031: unable to allocate 376 bytes of shared memory ("streams pool","unknow n object","streams pool","kwqbsinfy:cco")