Re: dbms_job problem

"Dirk Tschentscher" <dirkTHIS_at_REMvolkswagen.de> writes:
> I did a commit after the procedure.

At least one thing to check is that you might want to try dbms_job.run() your job several times and then check value of column BROKEN in view USER_JOBS as it may indicate something.

Easy way to shoot oneself to foot is to have different NLS parameters in different databases about what it comes to date formats and then construct a INTERVAL statement for the job that uses default date formats. I've done that. Ascii representations of dates and numbers should be avoided whenever possible. Try some simple interval like 'SYSDATE+(1/24)' that will work regardless if NLS parameters.

In some versions of the DB you had to dbms_job.run() your job once before it started to get run automatically but obviously you have done that.

-- 
Antti Järvinen, costello_at_iki.fi
             "concerto for two faggots and orchestra"