Re: Confusing CTXSYS issue

From: ddf <oratune_at_msn.com>
Date: Wed, 16 Sep 2009 12:21:57 -0700 (PDT)
Message-ID: <3a0226a7-2c84-416f-a766-132a7ec22459_at_f10g2000vbf.googlegroups.com>

On Sep 16, 1:21 pm, macdba321 <macdba..._at_gmail.com> wrote:
> 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.- Hide quoted text -
>
> - Show quoted text -

It would appear so. Check the documentation for DBMS_SCHEDULER to see if you can change the next_run_date to something more reasonable, or if you need to create a new job so the run schedule can be corrected.

David Fitzjarrell Received on Wed Sep 16 2009 - 14:21:57 CDT