Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: DBMS_JOB: different execution behaviour?
helo jeremy,
have a look at the source code would better, but okay. from your liners i read one thing that should be examined : you describe that you have implemented something like an exception description, iassume this is one of those exception statements from PL/SQL. can you tell me more about this, because i had a similar situation some weeks ago and i assume that the DBMS_JOB package will exit with such a condition.
best regards
burkhard schneider
Jeremy Ovenden schrieb:
>
> It appears that a program which is running under DBMS_JOB may execute
> differently to if it were running directly (e.g.) in sql*plus.
>
> A packaged procedure with no arguments is run every minute under dbms_job,
> and the job was submitted by user U. The procedure which runs actually
> processes 'requests' from a table records a status for each 'request' it
> processes to a table T. If an exception occurs during execution, the status
> of the 'request' is set to 'R' for retry. Strangely, when this procedure is
> executed by dbms_job, it is continually failing on a given 'request' and
> marking it as 'R'.
>
> When I run exactly the same procedure under sql*plus as user U, it executes
> perfectly and the 'request' is marked as completed successfully.
>
> As the procedure has no arguments, I can only assume that there are maybe
> some privilege-related issues somewhere, although obviously I would expect
> the procedure to execute as user U and with U's privileges in both cases....
>
> Any thoughts, chaps?
>
> Jeremy Ovenden
> HazelWeb Systems
> UK
Received on Wed Sep 15 1999 - 16:33:00 CDT
![]() |
![]() |