Re: DBMS_JOB.SUBMIT killing/cancelling a job

From: Mark D Powell <Mark.Powell_at_eds.com>
Date: 18 May 2007 13:28:18 -0700
Message-ID: <1179520098.352064.168190@y80g2000hsf.googlegroups.com>

On May 18, 11:04 am, jobs <j..._at_webdos.com> wrote:
> I have connection (from SQL Server SSIS) that launches and monitor
> jobs in Oracle (9i and 10g).
>
> I can tell if a job is currently running from a
>
> select * from all_jobs; in oracle.
>
> The cleanest/safest way to stop or cancel a job in oracle so that it
> disappears from all_jobs is and not doing anything any longer?

And the "cleanest/safest way to stop or cancel a job in oracle" is?

Where is the actual command you run? What happens when you submit it?

On the 10g instance you should be using dbms_scheduler to control jobs.

Full Oracle versions may be required for someone to help you with this since Oracle bugs are usually version specific as are when features became available.

Mark D Powell --

Received on Fri May 18 2007 - 15:28:18 CDT