Kill DBMS_SCHEDULER jobs

Hi,
How to kill a job which gave only job_name and owner. no other details like sid etc.. how to kill this job?
Regards

user738145 wrote:
I tried this, but it's still sunning .
SQL> exec DBMS_SCHEDULER.stop_JOB (job_name => 'MM.MM_WEEKLY_JOB');
PL/SQL procedure successfully completed.
SQL> exec DBMS_SCHEDULER.DROP_JOB (job_name => 'MM.MM_WEEKLY_JOB');
BEGIN DBMS_SCHEDULER.DROP_JOB (job_name => 'MM.MM_WEEKLY_JOB'); END;
ERROR at line 1:
ORA-27478: job "MM.MM_DAILY_JOB" is running
ORA-06512: at "SYS.DBMS_ISCHED", line 182
ORA-06512: at "SYS.DBMS_SCHEDULER", line 615
ORA-06512: at line 1
Edited by: user738145 on Sep 20, 2011 6:11 PMIf MM_WEEKLY_JOB was doing many, many DML,
then it may take a while to ROLLBACK all previously made changes

Similar Messages

How to kill a job in SM37

hi All,
can someone wxplain me how to kill a job in SM37 which is delaed by 10,000 secs.
cheers

Hi Rase,
goto SM37 and click on the active selection and enter the jobname and then click excute the particulr job should appear highlight the jobname then click on the stop iconthat appears on the taskbar( 3 rd from left)
or goto SM50 Click on the process and select process->stop without core
or
set a running infopack of the chain (in RSMO) to red, thats will stop the chain (if there are no parallels, else set all parallels to red).
****Assign Points If Helpful****
Regards,
Ravikanth

Can I set up a job that kills multiple jobs?

So, I've got some jobs that access a remote DB, and the link is not terribly reliable. When it hiccups, if a job is running, it hangs forever. Using this forum, I was able to set up a job that is triggered when a job goes over max duration, and it simply kills and restarts the job, it works great for the one job that typically runs long enough to get hit on a daily basis. This morning, I noticed one of the other jobs hung. So, I realize I can easily set up another kill job that gets fired off when this other job hangs, but what I'd really like to do is have one master kill job that can be used to kill any of several jobs so I don't have to have a kill job for each job that might get hung.
Is there a way to reference, in the PL/SQL block, any of the "tab" fields used in the condition block? I'd like to check tab.user_data.object_name in the PL/SQL block and kill/restart the appropriate job. So, my condition would be a generic event_type of JOB_OVER_MAX_DUR and would fire for any job meeting that condition. Possible? Feasible? Dangerous?

Thanks for the reply, Tom.
I am using version 10.2.0.4.
Point of clarification: I don't want to kill multiple jobs on one execution. I just want to write one job that can handle killing any one of the several jobs that I'm having issues with. So, for example, I have jobs A, B, and C. I want one snipe job that is generically called when anything raises a job_over_max_duration event, and it would figure out which job (A,B, or C) that is stuck and kill it.
From your reply, it sounds like I could do this in 11g, but probably not in 10g?
Thanks again!
---dale

Dbms_scheduler job neither succeeds nor errors its just keep running for ever

Hi All,
I am trying to run a shell script from plsql using the dbms_scheduler, job is getting created and it keeps running for ever without success or error.
Can some please help me where I am doing the mistake.
Thanks
DB Version:
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
Plsql Script:
BEGIN
   DBMS_SCHEDULER.create_job (
      job_name              => 'SFTP_PAYMENTECH_BATCHID1',
      job_type              => 'EXECUTABLE',
      job_action            => '/app07/ebdev/ebdevappl/xxtpc/bin/test.sh',
      number_of_arguments   => 1,
      enabled               => FALSE,
      auto_drop             => TRUE,
      comments              => 'SFTP Batch File to Paymentech');
   DBMS_OUTPUT.put_line (
      'Job Created Successfully:' || 'SFTP PAYMENTECH BATCHID');
   fnd_file.put_line (
      fnd_file.output,
      'Job Created Successfully:' || 'SFTP PAYMENTECH BATCHID');
   COMMIT;
   DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE (
      job_name            => 'SFTP_PAYMENTECH_BATCHID1',
      argument_position   => 1,
      argument_value      => '66667'                        /*v_printer_name*/
   DBMS_SCHEDULER.enable (name => 'SFTP_PAYMENTECH_BATCHID1');
EXCEPTION
   WHEN OTHERS
   THEN
      fnd_file.put_line (fnd_file.output,
                         'Error while creating the Job:' || SQLERRM);
      DBMS_OUTPUT.put_line ('Error while creating the Job:' || SQLERRM);
END;
Shell Script which I am calling:
#!/usr/bin/ksh
FILENAME=$1
PMTHOST=198.xx.xx.xx
PMTUSER=xxxxx
PMTPW=xxxxx
a='apps'
b='xxxxxx'
c='EBDEV'
INST=`echo $TWO_TASK | sed 's/_BALANCE//'`
echo INSTANCE: $INST
echo
File_Path=$XXTPC_TOP/iby/out
echo File Name: $FILENAME
echo $PMTHOST
echo $PMTUSER
echo
echo Date: `date`
echo
echo File System User: `whoami`
echo
echo Instance: $TWO_TASK
echo
echo File_Path: $File_Path
echo
echo PMT SFTP
# Fetch file using MBATCHID as File Name
cd $File_Path
echo
echo -----------------------------------------------
echo
echo Current File          :$FILENAME
l_date_time=`date +%Y%m%d%H%M%S`
echo SFTP Remittance File
# sftp $PMTUSER@$PMTHOST << EOF
lftp -u $PMTUSER,$PMTPW sftp://$PMTHOST << EOF
lcd $File_Path
cd test/945299
put $FILENAME
exit
EOF
#`sqlplus -s apps/tpcdev2013@EBDEV @try.sql $FILENAME`

Have you tried running the script manually to confirm it isnt just hanging on input for the lftp ?
You could add a -o <file> to the lftp command line which would output debug info into <file> so you could see.
Creation of the job looks fine so as GregV said, what output do you have in ALL_SCHEDULER_RUNNING_JOBS and any ADDITIONAL_INFO in the ALL_SCHEDULER_JOB_RUN_DETAILS or in $ORACLE_HOME/scheduler/log that might indicate what the problem is ?
If this answer was helpful, please mark as helpful answer.

Hi i have 50 infoobjects as part of my aggregates and in that 10 infoobjects have received changes in masterdata.so in my process chain the Attribute change run in running for a long time.can i kill the job and repeat the same.

Hi i have 50 infoobjects as part of my aggregates and in that 10 infoobjects have received changes in masterdata.so in my process chain the Attribute change run in running for a long time.can i kill the job and repeat the same.

Hi,
I believe this would be your Prod system, so don't just cancel it but look at the job log. If it is still processing then don't kill it and wait for the change run to complete but if you can see that nothing is happening and it is stuck for a long time then you can go ahead and cancel it.
But please be sure, as these kind of jobs can create problems if you cancel them in the middle of a job.
Regards,
Arminder Singh

"Who ran me" - how to determine the name of the dbms_scheduler job that ran me

Hi Community
I can see plenty of examples out on the interweb which shows how you can use dbms_utility.format_call_stack to find the hierarchy of procs, functions and packages that got me to a particular point in my code.
For example, if proc (procedure) A calls proc B, which in turn calls proc C, in the code for proc C, I can query the call stack to find out that proc C was called by proc B which in turn was called by proc A
However, I want to extend this further.
For example, using the example above, if proc A in turn was started by a dbms_scheduler job, I want to determine (within proc C) the name of the dbms_scheduler job which started the whole process off.
The reason I want to do this is that I have inherited a (massive) system which is undocumented. In many places within the code, email alerts are sent out using a custom "MAIL" package to designated users (now including me) when certain long-running processes reach certain milestones and/or complete.
I have added to the custom "MAIL" package a trailer on the mails to show the call stack. I also want to show the name of the dbms_scheduler job which started it all.
Over time, this info may help me in building the "map" of how the whole undocumented system hangs together and in the meantime, to assist in troubleshooting problems
Looking forward to hearing from you
Alan

Use USER_SCHEDULER_RUNNING_JOBS or DBA_SCHEDULER_RUNNING_JOBS there is column SESSION_ID and when you know your session ID build query is very simple.
select owner, job_name
into ...
from dba_scheduler_runnig_jobs
where session_id=sys_context('USERENV','SESSIONID');
You must declare local variables in PL/SQL procedure to read owner and job_name into them. Second thing, you must handle possible exception no_data_found than can be raised when procedure is not run from job.

Exclude DBMS_SCHEDULER jobs in DATA PUMP import

Hello,
I need to exclude all DBMS_SCHEDULER jobs during DATA PUMP import.
I tried to do this with: EXCLUDE=JOB but this only works on DBMS_JOB.
Is there a way to exclude all DBMS_SCHEDULER jobs during import?
Kind Regards

There are PROCOBJ that can be excluded (Procedural objects in the selected schemas) but I'm affraid it exclude not only DBMS_SCHEDULER jobs.
Any ideas?

DDL for DBMS_SCHEDULER job

How do I generate the DDL for an existing DBMS_SCHEDULER job? I've tried using DBMS_METADATA.GET_DDL, but that doesn't seem to work with the scheduler jobs.

Susan's method is probably the best.
Another slightly more clunky way is to export the user's schema (using expdp) and then use impdp with the SQLFILE option, so the generated file will then contain the DDL to create the job.
Note than none of these methods will work if you have set non-varchar2 (i.e. object) argument values for the job.
Hope this helps,
Ravi.

Kill a job with status "Ready"

HI all,
Is there any way that I can delete or cancel a job which has a status "Ready"?
Thanx in advance.
Rgds
Lalit Rana

please only post your question in 1 forum.
I answered you at How to kill a job in "Ready" status.

Killing a job in "Ready" Status

HI all,
Is there any way that I can delete or cancel a job which has a status "Ready"?
Thanx in advance.
Rgds
Lalit Rana

please only post your question in 1 forum.
I answered you at How to kill a job in "Ready" status.

Query to get script for dbms_scheduler jobs

Hi,
I created 3 dbms_scheduler jobs on customer DB earlier. Now with the latest version of Toad they have, when I try to describe these jobs it gives me an error saying ADMIN MODULE REQUIRED to describe such objects.
I contacted Toad for the same and they asked the customer to purchase ADMIN MODULE which th customer is not willing.
My problem is that I need the scipts of each of these DBMS_SCHEDULER jobs and programs, However I am not able to locate a DATA DICTIONARY that would store the source for each of them like we have for PROCEDURES etc USER_SOURCE data dictionary.
Is anyone aware of any such Data Dictionary or has a quey though which I can retrive Scheduler Jobs and Programs scripts.
Please Help.

Ok got it :)
To show details on job run:
select log_date
, job_name
, status
, req_start_date
, actual_start_date
, run_duration
from dba_scheduler_job_run_details;
To show running jobs:
select job_name
, session_id
, running_instance
, elapsed_time
, cpu_used
from dba_scheduler_running_jobs;
To show job history:
select log_date
, job_name
, status
from dba_scheduler_job_log;
show all schedules:
select schedule_name, schedule_type, start_date, repeat_interval
from dba_scheduler_schedules;
show all jobs and their attributes:
select *
from dba_scheduler_jobs;
show all program-objects and their attributes
select *
from dba_scheduler_programs;
show all program-arguments:
select *
from dba_scheduler_program_args;
Thanks

Procedure doesn't work in a DBMS_SCHEDULER job

I have a problem with an dbms_scheduler job.
We have a procedure with a select and the follwing where clause
and tb.geaendert_am >= systimestamp - interval '5' minute;
The column tb.geaendert_am is a timestamp column and means changed_on.
That procedure we call in a dbms_scheduler job, which runs every 5 minutes.
What we want is to collect all rows which are new since last job run.
Now happens following
The job run and collect all rows, also row alter than 5 Minute.
On every run the procedure collect all old and new rows.
When we run the procedure manually, also the single select, we get the correct collection of all rows which are new since last job run.
Have anyone a idea?
I now the where clause is not perfect and we have some more inconsistency.
(At the first run we don't get all rows which older than 5 minutes before systimestamp)
In the moment we discuss if it make more since to mark the rows which we have collected.
But that is not the question, the question is why a soure manually works well
and when it runs in the Job we have a wrongness.
Thanks in advanced.
Regards
Michael

Hi Sven
thanks for answering.
I told you what is wrong ;-)
My select with the where "systimestamp - interval '5' minute" clause runing well.Every time I get only new rows
That select is implemented in a procedure. Starting the procedure from sqlplus or sqldeveloper, the select running well.I get only new rows.
But when it would be started by dbms_scheduler we get everytime all rows, the old, also the new rows.
When I start the Procedure shortly after the job or parallel to the job my select shows only the new rows which are not older than 5 Minutes
Conclusion, when the procedure would be startet by the job we get to much rows.
The difference is, one runs on the database server, one runs on an client.
I have considered also to mark the data set with select for update. But I see following issues.
1) The job is for an monitoring tool, that tool would be not discrete anymore.
2) What happen in a case with an error, "for update of" lock only a new column which I add to mark the rows.
Perhaps I get a impact in the application that it must not happen. The application is very time sensitive.
3) What is with the transaction, my procedure must be anonymous.
It is shure that we get no effect in application?
Our java application communicate with a lot of other application, partly java aplication, partly Oracle BPEL applications.
So our monitoring tool should not interrupt the sensitive chain.
Regards,
Michael
Edited by: MichaelMerkel on 11.03.2011 02:15

Can't kill a job in Reports Server 9i

i have installed Oracle 9ias release 2 patch 3 under winnt.
i review the current jobs queue of my report server and i have a job started since two day ago. i try to kill that job use a command like this
http://servername/reports/rwservlet/killjobid1281?server=servername
and i recieved the following error
can't kill the job with id 1281REP-50125: Excepción obtenida: org.omg.CORBA.UNKNOWN: minor code: 0 completed: No
anybody can help me? i want to kill this job without have to restart the Report service

time for process identification and pskill I think

Generating PDF Report and Mailing from APEX through DBMS_SCHEDULER job

Hi,
We have a requirement to generate pdf reports and mail them from our apex app through a DBMS_SCHEDULER job. The DBMS_SCHEDULER job calls a PL/SQL procedure which has the logic for calling the APEX_UTIL.GET_PRINT_DOCUMENT API (Function Signature 3) passing the application_id, the report_query_name and the report_layout_name to generate the pdf report output. The APEX_UTIL.GET_PRINT_DOCUMENT call is returning NULL when called from the DBMS_SCHEDULER job (It doesn't throw any exception as well!). But the same procedure when called from an APEX App Page Process that is invoked on an event like a Button click, the API returns the PDF report output.
I am also setting the APEX workspace security_group_id at the beginning of the PL/SQL procedure as follows:
l_workspace_id := apex_util.find_security_group_id (p_workspace => 'MY_WORKSPACE');
apex_util.set_security_group_id (p_security_group_id => l_workspace_id);
Any idea on what might be going wrong? Any alternative ways to generate the report output in the PL/SQL procedure?
Thanks & Regards,
Sujesh K K

I was able to do a workaround for this issue by rebooting the DB.
As per ID 579281.1, this is a bug in 11.1.0.6 and we need to upgrade the version to 11.1.0.7 or apply a one -off patch.
Thanks,
Arun

Dbms_Parallel_Execute run as a Dbms_Scheduler job

Hi,
I have tried to use Dbms_Parallel_Execute to update a column in different tables.
This works fine when I run it from SQLPlus or similar.
But if I try to run the code as a background job using Dbms_Scheduler it hangs on the procedure Dbms_Parallel_Execute.Run_Task.
The session seems to hang forever.
If I kill the session of the background job, the task ends up in state FINISHED and the update has been completed.
If I look on the session it seems to be waiting for event "pl/sql lock timer".
Anyone who knows what can go wrong when running this code as a background job using Dbms_Scheduler?
Code example:
CREATE OR REPLACE PROCEDURE Execute_Task___ (
table_name_ IN VARCHAR2,
stmt_ IN VARCHAR2,
chunk_size_ IN NUMBER DEFAULT 10000,
parallel_level_ IN NUMBER DEFAULT 10 )
IS
task_ VARCHAR2(30) := Dbms_Parallel_Execute.Generate_Task_Name;
status_ NUMBER;
error_occurred EXCEPTION;
BEGIN
Dbms_Parallel_Execute.Create_Task(task_name => task_);
Dbms_Parallel_Execute.Create_Chunks_By_Rowid(task_name => task_,
table_owner => Fnd_Session_API.Get_App_Owner,
table_name => table_name_,
by_row => TRUE,
chunk_size => chunk_size_);
-- Example statement
-- stmt_ := 'UPDATE Test_TAB SET rowkey = sys_guid() WHERE rowkey IS NULL AND rowid BETWEEN :start_id AND :end_id';
Dbms_Parallel_Execute.Run_Task(task_name => task_,
sql_stmt => stmt_,
language_flag => Dbms_Sql.NATIVE,
parallel_level => parallel_level_);
status_ := Dbms_Parallel_Execute.Task_Status(task_);
IF (status_ IN (Dbms_Parallel_Execute.FINISHED_WITH_ERROR, Dbms_Parallel_Execute.CRASHED)) THEN
Dbms_Parallel_Execute.Resume_Task(task_);
status_ := Dbms_Parallel_Execute.Task_Status(task_);
END IF;
Dbms_Parallel_Execute.Drop_Task(task_);
EXCEPTION
WHEN OTHERS THEN
Dbms_Parallel_Execute.Drop_Task(task_);
RAISE;
END Execute_Task___;

Hi,
Check job_queue_processes parameter, it must be greater than 0.

Kill DBMS_SCHEDULER jobs

Similar Messages

Maybe you are looking for