I located the job, sid, serial#, and spid of the job that was running.
I logged on as the user who created the job and successfully ran EXEC DBMS_JOB.BROKEN(10483,TRUE);
I successfully rant ALTER SYSTEM KILL SESSION '156,6680';
On the server I ran kill '9 656940 and confirmed the process was gone.
But it immediately spawned a new job/process
When I log on as the user who created the job and query user_jobs
I see that job 10483 just started even though it has a next-date of 4000-01-01 and broken = Y
As DBA, when I query dba_jobs the job 10483 has a next_date of 2009-02-13 and broken = N