Re: Job submitted via dbms_job, when does it first run?
Date: 1998/01/19
Message-ID: <0ClzvDA8nyw0Mw$C_at_camk.demon.co.uk>#1/1
In article <34bfd7a4.13544448_at_www.sigov.si>, Jurij Modic
<jurij.modic_at_mf.sigov.mail.si> writes
>On Fri, 16 Jan 1998 12:13:30 +0000, Andy Hardy
><Andy_Hardy_at_camk.demon.co.uk> wrote:
>
>>From the available documentation, I thought that a job entered via
>>dbms_job would run immediately(ish) and then at the defined 'interval'.
>>
>>In practice, it appears that the job is only run for the first time when
>>you call dbms_job.run.
>>
>>Is this true, or am I experiencing local difficulties?
>
>After you submit a job using DBMS_JOB package, you must execute a
>COMMIT if you want to execute it automaticaly. Or alternatively, run
>DBMS_JOB.RUN, which is the only procedure from this package that
>contains implicit COMMIT.
Ah... clunk and the penny drops.
Thanks,
Andy
-- Andy Hardy Senior IT Systems Engineer Cegelec AEG ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Opinions are mine and do not necessarily reflect those of Cegelec AEGReceived on Mon Jan 19 1998 - 00:00:00 CET