RE: dbms_job not Working

That did it. job_queue_processes was set to zero in the init.ora file. I didn't apply the CPU (the other DBA here did), but are you saying that part of applying the CPU set the parameter to zero?

I altered the system to set this parameter to 2, and I also changed the init.ora parameter.

Thanks everybody for your responses.

Sam Bootsma
Oracle Database Administrator
Information Technology Services
George Brown College
Phone: 416-415-5000 x4933
Fax: 416-415-4836
E-mail: sbootsma_at_georgebrown.ca

-----Original Message-----
From: Alberto Dell'Era [mailto:alberto.dellera_at_gmail.com] Sent: March 8, 2007 5:42 PM
To: Sam Bootsma
Subject: Re: dbms_job not Working

Haven't you set job_processes to zero as part of the patch apply, and forgot to set it back perhaps ?

"job_processes", I mean the parameter that dictates the number of job processes to be created ... don't remember if that's exactly the name, sorry but it's night here and I'm very tired ;(

On 3/8/07, Sam Bootsma <sbootsma_at_georgebrown.ca> wrote:
>
>
>
>
> I have a job named checkwaits that I schedule to run every two minutes
using
> dbms_jobs. This worked smoothly until early January when we applied
the
> October CPU. After this, it stopped working, but I didn't know it
stopped
> working until just today. I removed the job and resubmitted it, but
it is
> still not running the job according to the schedule. If I manually
run the
> job using "exec dbms_job.run(62);" it does execute.
>
>
>
> Here is the script I used to re-submit the job (logged on as user
dbatools):
>
>
> -- Submit to run every 2 minutes:
>
> variable jobno number;
>
> begin
>
>

dbms_job.submit(:jobno,'dbatools.checkwaits;',sysdate+1/1440,'sysdate +
> 2/1440');
>
> commit;
>
> end;
>
> /
>
>
>
> Then I query dba_jobs while logged on as system:
>
> system_at_PROD> l
>
> 1 select job, log_user, priv_user, last_date, last_sec, next_date,
> next_sec, broken,
>
> 2 interval, failures, what
>
> 3 from dba_jobs
>
> 4* where job=62
>
> system_at_PROD> /
>
>
>
> LOG_USER PRIV_USER LAST_DATE LAST_SEC
> NEXT_DATE NEXT_SEC B INTERVAL FAILURES
>
> ---------- ------------------------------ ------------------- --------
> ------------------- --------
>
> WHAT
>
> --------------------
>
> DBATOOLS DBATOOLS
> 2007-03-08 16:53:06 16:53:06 N sysdate + 2/1440
>
> dbatools.checkwaits;
>
>
>
>
>
> So even though the next_date is set to 1 minute in the future when the
job
> is submitted, it is not run (not even 20 minutes afterwards).
>
>
>
> Can anybody point me in the right direction on how I can get this
working
> again.
>
>
>
> Thanks,
>
>
>
> Sam Bootsma
>
> Oracle Database Administrator
>
> Information Technology Services
> George Brown College
>
> Phone: 416-415-5000 x4933
> Fax: 416-415-4836
> E-mail: sbootsma_at_georgebrown.ca
>
>

-- 
Alberto Dell'Era
"Per aspera ad astra"
--
http://www.freelists.org/webpage/oracle-l