Re: complex dbms jobs code

You might set other DBMS_JOBs to break the first, and yet another to reenable it later.

dbms_job.broken(125,TRUE);

later:

dbms_job.broken(125,false);

I've inherited applications that have this set. I don't like them personally. The new applications that I've been involved in building, are bulletproofed so that they can run 24/7.

Another possibility is to use a sql script, and set the frequency in unix cron or NT scheduler.

willjamu_at_mindspring.com (James A. Williams) wrote in message news:<3cd11271.1077108_at_news.mindspring.com>...
> Oracle 8.1.7.3 on Solaris. I have the below. I need to run a job
> Monday through Thursday . It needs to run every 30 minutes at 00
> and 30 minutes after each hour. The below only schedule for 12:30
> each day. Any help on improving the interval to get this to work
> would be cool!
>
>
> VARIABLE jobno number;
> BEGIN
> sys.dbms_job.submit(:jobno,
> 'aglcust.lookup_update.cas_schedule;',
> sysdate,
> 'TRUNC(LEAST(NEXT_DAY(SYSDATE,''MONDAY''),
> NEXT_DAY(SYSDATE,''TUESDAY''),
> NEXT_DAY(SYSDATE,''WEDNESDAY''),
> NEXT_DAY(SYSDATE,''THURSDAY'') ) ) + 30/1440');
> END;
>
>
>
>
> JOB LOG_USER PRIV_USER SCHEMA_USER LAST_DATE
> LAST_SEC THIS_DATE THIS_SEC NEXT_DATE
> NEXT_SEC TOTAL_TIME BROKEN INTERVAL FAILURES
> WHAT NLS_ENV MISC_ENV INSTANCE
> 125 AGLCUST AGLCUST AGLCUST 5/2/2002 12:30:29 AM 00:30:29
> 5/6/2002 12:30:00 AM 00:30:00 653 N
> TRUNC(LEAST(NEXT_DAY(SYSDATE,'MONDAY'),
> NEXT_DAY(SYSDATE,'TUESDAY'),
> NEXT_DAY(SYSDATE,'WEDNESDAY'),
> NEXT_DAY(SYSDATE,'THURSDAY') ) ) + 30/1440 0
> aglcust.lookup_update.cas_schedule; NLS_LANGUAGE='AMERICAN'
> NLS_TERRITORY='AMERICA' NLS_CURRENCY='$' NLS_ISO_CURRENCY='AMERICA'
> NLS_NUMERIC_CHARACTERS='.,' NLS_DATE_FORMAT='YYYYMMDD'
> NLS_DATE_LANGUAGE='AMERICAN' NLS_SORT='BINARY' 0102000200000000
> 0
Received on Thu May 02 2002 - 09:54:04 CDT