DBMS_SCHEDULER.STOP_JOB

Question

Hi,
I have created a external job to execute exe's in unix box. The steps followed are as follows:
    DBMS_SCHEDULER.CREATE_JOB (
                          job_name=>v_job_name,
                          Job_Type => 'EXECUTABLE',
                          Job_Action => exe_name,
                          Enabled=>FALSE,
                          credential_name=>u_name,
                          number_of_arguments=>3);
    DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(v_job_name,1,file_name);
    DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(v_job_name,2,job_name);
    DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(v_job_name,3,job_request_id);
    DBMS_SCHEDULER.RUN_JOB(v_job_name, TRUE);
The job is created and in unix box the exe is invoked successfully,,,
During this particular time when the unix box exe is still running, if I issue
BEGIN
          DBMS_SCHEDULER.STOP_JOB ( job_name=>kill_job_name , force=> true );
END;
The job is not stopped and the below error message is shown...
ORA-27366: job "140225_4202261012171102" is not running
ORA-06512: at "SYS.DBMS_ISCHED", line 199
ORA-06512: at "SYS.DBMS_SCHEDULER", line 557
ORA-06512: at line 2
27366. 00000 -  "job \"%s.%s\" is not running"
*Cause:    An attempt was made to stop a job that was not running.
*Action:   Verify the status of the job. If the job is running but this
           message is still being returned, contact Oracle support.
Also after sometime the unix box exe completes successfully. This is visible in dba_scheduler_job_run_details - SUCCEEDED..
Please provide your valuable inputs.
Regards,
VM

Answer 1

Do you stop the job with the same user as the owner's?
YES - the owner of  the job remains the same.
(You said "DBA_SCHEDULER_RUNNING_JOBS is not showing any entry till the unix box exe completes.")
--> Yes dba_scheduler_jobs has entries available - STATE column value in DISABLED and no entry were available in dba _Scheduler_running_jobs : Also when checked in unix box it is in running status.
  recap of the code and error reported
BEGIN
DBMS_SCHEDULER.CREATE_JOB (
                          job_name=>v_job_name,
                          Job_Type => 'EXECUTABLE',
                          Job_Action => exe_name,
                          Enabled=>FALSE,
                          credential_name=>u_name,
                          number_of_arguments=>3);
    DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(v_job_name,1,file_name);
    DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(v_job_name,2,job_name);
    DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(v_job_name,3,job_request_id);
    DBMS_SCHEDULER.RUN_JOB(v_job_name, TRUE);
END;
BEGIN
          DBMS_SCHEDULER.STOP_JOB ( job_name=>'140226_5002261313171138' , force=> true );
END;
Error report -
ORA-27366: job "140226_5102261421171151" is not running
ORA-06512: at "SYS.DBMS_ISCHED", line 199
ORA-06512: at "SYS.DBMS_SCHEDULER", line 557
ORA-06512: at line 2
27366. 00000 -  "job \"%s.%s\" is not running"
*Cause:    An attempt was made to stop a job that was not running.
*Action:   Verify the status of the job. If the job is running but this
           message is still being returned, contact Oracle support.
Also I have come across one thread which is not exactly same as mine but has something in it
ORA-27366: job is not running.
Has anyone come across this thread.
Your help and suggestion is very much appreciated.