RE: Lazy dbms_job

>From my observations, it takes some time for the Oracle dbms_job processes
to kick off your job if they're busy with something else. That's probably where your delay is coming from. One workaround would be a job that runs continually in a loop and executes the 3 procedures ASAP. I don't know that it's advisable to let a job run forever, so you could have the loop terminate itself every 5 minutes or so to give the database a chance to "breath".

Thanks,
Jon Knight

 -----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Ranko Mosic

Sent:	Thursday, April 21, 2005 8:25 AM
To:	oracle-l_at_freelists.org
Subject:	Lazy dbms_job

I am running following procedure ( Oracle 9i ):=20

dbms_job.submit( l_job, 'background_submit_proc( JOB, NEXT_DATE);' );

create or replace

    procedure background_submit_proc( p_job in number, p_NEXT_DATE OUT DATE=   )
    as
    begin

               uui(); -- these are procedures that are executed;
               uui1();=20
               uui2();

=09p_next_date :=3D sysdate + 1/24/60/60*1;

    exception when others then raise;
end;
/

Whole thing runs fine. It modifies NEXT_DATE so it reschedules itself as soon as
3 procedures are finished. Procedures are very fast ( takes less than a second to execute them ). So job's NEXT_DATE should be incremented almost every second.
It is not. It is incremented every 15 seconds.=20 Is there a way to make it more responsive ? I want it to execute every seco= nd .=20

Regards, Ranko.

--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l