Re: Errors running scheduled job

From: DA Morgan <damorgan_at_x.washington.edu>
Date: Mon, 18 Apr 2005 12:55:49 -0700
Message-ID: <1113853926.788303@yasure>

Paul BJ wrote:

> Us mere database developers do not have access to the alert log (on the Unix
> box)...we have to ask a DBA and none were available before I left work this
> evening.
> 
> There was no error message as such...but the failure count on the JOB screen
> in Toad was incremented each time it ran and of course the desired changes
> were not implemented.
> 
> The thing I find most perplexing is the fact that if I run the Job manually
> (by rt clicking on the job in Toad and selecteing execute it works just fine
> and the result is what we want. What then, I ask myself is the difference
> between doing that and the scheduler doing the same thing which always
> fails.
> 
> Cheers
> 
> Paul
> 
> 
> "DA Morgan" <damorgan_at_x.washington.edu> wrote in message
> news:1113844998.958242_at_yasure...
> 

>>Paul BJ wrote:
>>
>>
>>>Oracle 9i on Unix (HP-UX I think).
>>>
>>>I have just written a job to run each day at 23:55.
>>>
>>>
>>>If I execute the code in the SP on its own it executes OK and produces

> 
> the
> 


>>>desired result.

>>>
>>>If I Right click on the job and select execute, it executes OK and

> 
> produces
> 


>>>the desired result.

>>>
>>>But when the job runs at 23:55 (or indeed at any other time ; we have

> 
> tried
> 


>>>lots of different times) it always fails.

>>>

>>>The code for the job is:

>>>begin

>>>

>>>sys.dbms_job.change(job => :job, what => :what, next_date => :next_date,

>>>interval => :interval); end;

>>>

>>>:JOB=763

>>>

>>>:WHAT=LUXPROJECT.SP_RESET_EXEC_TIME;

>>>

>>>:NEXT_DATE=04/18/2005 6:18:08 PM

>>>

>>>:INTERVAL=SYSDATE+30/1440

>>>
>>>(the interval has testing params in it but the result is the same if we

> 
> use
> 


>>>the real params; run once per day at 23:55)

>>>

>>>

>>>

>>>The SP contains:

>>>

>>>Update ad_parameters

>>>

>>>Set Loading_start_time = '00:01';

>>>

>>>commit;

>>>

>>>Anyone know what the problem might be?

>>>

>>>TIA

>>>
>>>Paul BJ
>>
>>With what error message?
>>With what written to the alert log?
>>--
>>Daniel A. Morgan
>>University of Washington
>>damorgan_at_x.washington.edu
>>(replace 'x' with 'u' to respond)

I'd suggest getting out of TOAD and working with SQL*Plus on this one. Without the error message not much help is possible.

One thought though is one of permissions. Is there explicit execute to the user of the procedure ... not execute via a role?

Oh and please don't top post. Thanks.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)

Received on Mon Apr 18 2005 - 14:55:49 CDT