Yes. If you really want to kill the job, the graceful way is to break it
first (dbms_job.broken) and then remove it (dbms_job.remove).
Scott Shafer
San Antonio, TX
210.581.6217
-Original Message-
From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]
Sent: Thursday, August 14, 2003 10:00
correct but the job stays in dba_jobs_running.
im assuming it completes or fails correct, but wont go back in the jobs$ table?
From: Hemant K Chitale [EMAIL PROTECTED]
Date: 2003/08/14 Thu AM 11:29:23 EDT
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: what happens
Yep. That sounds like your MO :)
Henry
-Original Message-
[EMAIL PROTECTED]
Sent: Thursday, August 14, 2003 12:19 PM
To: Multiple recipients of list ORACLE-L
Yes. If you really want to kill the job, the graceful way is to break it
first (dbms_job.broken) and then remove it
If the job is running, I think you have to kill the session running the job
after removing the job.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Stephen Lee
INET: [EMAIL PROTECTED]
Fat City Network Services-- 858-538-5051 http://www.fatcity.com
San Diego,
I think that you will see it disappear from the dba_jobs view, though.
Hemant
At 06:59 AM 14-08-03 -0800, you wrote:
If I run dbms_job.remove on a job that is in dba_jobs_running it remains
in that table.
it runs to completion correct?
--
Please see the official ORACLE-L FAQ:
That will not kill a job which is currently executing. It simply removes it from the
queue. The only way I know to kill a running job is to kill the associated job queue
process on the server.
Ian MacGregor
Stanford Linear Accelerator Center
[EMAIL PROTECTED]
-Original Message-