Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I get the error below when importing a database - any ideas why? I do this type of import all the time and I've never seen this error.

Prior to doing the import we drop all objects in the schema. The import always fails when importing the same table..

  [exec] IMP-00017: following statement failed with ORACLE error 1:
     [exec] "BEGIN   DBMS_JOB.ISUBMIT(JOB=>99,WHAT=>' quemon();',NEXT_DATE=>TO_DATE('400"
     [exec] "0-01-01:00:00:00','YYYY-MM-DD:HH24:MI:SS'),INTERVAL=>'SYSDATE + 1/144 /* 1 "
     [exec] "Hour */',NO_PARSE=>TRUE); END;"
     [exec] IMP-00003: ORACLE error 1 encountered
     [exec] ORA-00001: unique constraint (SYS.I_JOB_JOB) violated
     [exec] ORA-06512: at "SYS.DBMS_JOB", line 97
share|improve this question

You already have a job in the target database that is numbered 99. You'll need to drop that job.

Edit: The ISUBMIT procedure of dbms_job is a bit hard to find docs on. Here is where I found some. That procedure submits a job with a specified job number, whereas the SUBMIT procedure assigns a job number for you, avoiding this very problem. To remove the offending job (in your case), run:

execute dbms_job.remove(99);
share|improve this answer
Trying that ... – Marcus Leon Nov 18 '09 at 22:56
Be careful if you choose to remove a job using DMBS_JOB.REMOVE(), since you don't know exactly what job you remove, in which schema. Simply use first DCookie's suggestion: use DBMS_JOB.SUBMIT() instead of DBMS_JOB.ISUBMIT() which will always create a new job, so no risk :) See also… – Frosty Z Mar 18 '13 at 9:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.