Re: Confusing CTXSYS issue
From: Shakespeare <whatsin_at_xs4all.nl>
Date: Thu, 17 Sep 2009 07:53:32 +0200
Message-ID: <4ab1cee2$0$83238$e4fe514c_at_news.xs4all.nl>
macdba321 schreef:
> On Sep 16, 1:13 pm, ddf <orat..._at_msn.com> wrote:
>
> The repeat_interval for both jobs is identical: TRUNC(SYSDATE)+1
> That would lead me to believe that it's attempting midnight each
> night.
> The next_run_date for both jobs however is: '26-MAR-12 09:46.40.000000
> AM -05:00'
>
> So does this mean it's valid and scheduled ... just for 2012?
>
> Thanks again.
Date: Thu, 17 Sep 2009 07:53:32 +0200
Message-ID: <4ab1cee2$0$83238$e4fe514c_at_news.xs4all.nl>
macdba321 schreef:
> On Sep 16, 1:13 pm, ddf <orat..._at_msn.com> wrote:
>> On Sep 16, 11:50 am, macdba321 <macdba..._at_gmail.com> wrote: >> >>> Interesting... >>> select job_name, last_start_date, next_run_date from >>> dba_scheduler_jobs; >>> DR$IDX_RY_RESOURCE_META$J >>> 24-JAN-09 12.00.00.107000 AM -05:00 >>> 26-MAR-12 09.46.40.000000 AM -05.00 >>> So does this mean that it is schedule, but to run next in 2012? >>> Thanks again. >> Yes. What does the repeat_interval column report? It should display >> the frequency and the interval to use. That value may need to be >> changed to get the job to run on a more frequent (and current) basis. >> You can use the DBMS_SCHEDULER.SET_ATTRIBUTE procedure to make such >> changes. >> >> David Fitzjarrell
>
> The repeat_interval for both jobs is identical: TRUNC(SYSDATE)+1
> That would lead me to believe that it's attempting midnight each
> night.
> The next_run_date for both jobs however is: '26-MAR-12 09:46.40.000000
> AM -05:00'
>
> So does this mean it's valid and scheduled ... just for 2012?
>
> Thanks again.
Maybe I'm confused here, but should not the interval be a number of days instead of a date?
Shakespeare Received on Thu Sep 17 2009 - 00:53:32 CDT