I was able to get the job removed. It was left over from an application upgrade, so it doesn't need to be migrated. Thank you to everyone, your answers were extremely helpful! Scott Canaan '88 (srcdco@xxxxxxx<mailto:srcdco@xxxxxxx>) (585) 475-7886 - work (585) 339-8659 - cell "Life is like a sewer, what you get out of it depends on what you put into it." - Tom Lehrer From: Maaz Anjum [mailto:maazanjum@xxxxxxxxx] Sent: Friday, April 04, 2014 4:14 PM To: jure.bratina@xxxxxxxxx Cc: Mark Bobak; Scott Canaan; oracle-l@xxxxxxxxxxxxx Subject: Re: Jobs Question Would you consider migrating to DBMS_SCHEDULER from DBMS_JOBS? Tim Hall, wrote about it (the 10g version) a few years ago but it is still relevant. http://www.oracle-base.com/articles/10g/scheduler-10g.php Cheers, Maaz On Fri, Apr 4, 2014 at 3:51 PM, Jure Bratina <jure.bratina@xxxxxxxxx<mailto:jure.bratina@xxxxxxxxx>> wrote: Or you can use the DBMS_IJOB.REMOVE procedure as described here: http://oradbatips.blogspot.com/2010/05/tip-87-createremove-jobs-for-other.html Regards, Jure On Fri, Apr 4, 2014 at 8:29 PM, Mark Bobak <Mark.Bobak@xxxxxxxxxxxx<mailto:Mark.Bobak@xxxxxxxxxxxx>> wrote: I believe you need to be connected as the user who created the job. -Mark -- A life yet to be lived...