Re: dbms_job problem

Hi,
I did a commit after the procedure.

Dirk

"Vladimir M. Zakharychev" <bob_at_dpsp-yes.com> schrieb im Newsbeitrag news:b1o38v$ee6$1_at_babylon.agtel.net...
> You need to commit after submitting the job.
>
> --
> Vladimir Zakharychev (bob_at_dpsp-yes.com)
http://www.dpsp-yes.com
> Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet
applications.
> All opinions are mine and do not necessarily go in line with those of my
employer.
>
>
> "Dirk Tschentscher" <dirkTHIS_at_REMvolkswagen.de> wrote in message
> news:b1o0tj$h5d1_at_doiweb4.volkswagen.de...
> > Hello !
> > We've got two databases
> > Test 8.1.6.0.0 (where I have dba access) with Windows NT 40 SP6
> > prod 8.1.7.2.0 (where I don't have dba access) some kind of Unix
(I
> > don't know...)
> > with the identical parameters
> > job_queue_interval = 60 and
> > job_queue_processes = 10.
> >
> > I submit my job with the following procedure :
> >
> > Procedure zz_job_start is
> > jobno number;
> > BEGIN
> > dbms_job.submit(jobno,'STAMM_AUFTRAEGE_ABARBEITEN;',
> > sysdate,'sysdate + (1/(30*24))'); -- alle 2 Minuten
> > EXCEPTION WHEN others THEN
> > dbms_output.put_line(sqlerrm);
> > END;
> >
> > In the test environment, everything works fine,
> > but in prod nothing happens...
> >
> > I can start the job with dbms_job.run, then the job works correct,
> > but it doesn't run the next time...
> >
> > Has anyone a hint what I can do ?
> >
> > Rgds
> > Dirk
> >
> >
> >
> >
> >
>
Received on Tue Feb 04 2003 - 04:12:15 CST