| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> c.d.o.server -> Re: running dbms_job on behalf of an other user
In article <37219ec7.12808247_at_192.86.155.100>,
tkyte_at_us.oracle.com wrote:
> A copy of this was sent to sybrandb_at_my-dejanews.com
> (if that email address didn't require changing)
> On Tue, 20 Apr 1999 14:42:49 GMT, you wrote:
>
> [sniped]
> yes, that is correct. dbms_job runs with the entire environment of the user
> submitting the job (NLS settings, user, etc are all preserved). Since you are
> submitting a stored procedure to be executed tho, the procedure itself runs
with
> the priveleges of the CREATOR not the current user (until Oracle8i that is
when
> you get to pick how it runs -- as invoker or as definer).
>
>
> they didn't fail -- they succeeded. If you submit a job with a time to run
and
> a 'what' and that job you submit runs without raising an exception, it is
> removed from the queue.
>
> If the job failed due to an unhandled exception:
>
> o a message to that effect would have been recorded in your alert log
> o the job would stay in the queue with the FAILURES column incremented. It
> would be retried later.
>
> I think you need to add some debug to your jobs you are running in the
> background (eg: put an insert and commit at the end if it -- in the block
that
>
[sniped]
something else is happening, the
jobs
> wont just 'disappear' if they fail with an error (otoh -- they will just
> disappear if they run sucessfully and have no 'next' date).
> [sniped]
[sniped]>
Actually, I did inadvertently leave out the 'next' date. Thanks! I am now looking at strange differences in time between server and clients, this has probably more to do with a combination of non-synchronized system clocks and a high job_queue_interval than problems in dbms_job. It looks like the job is functioning properly. I found a way to patch the code: I now verify whether I own the table which should be purged. If I don't own that table, I don't verify the existence of that particular job. This will make sure the job is submitted by the schema owner only.
Best regards,
Sybrand Bakker, Oracle DBA
-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Wed Apr 21 1999 - 04:22:37 CDT
![]() |
![]() |