1) Create a dbms_scheduler job (e.g TEST) and only put in a schedule_limit.
2) Run the below SQL -> the schedule_limit is set, but the run duration isn’t as expected.
select job_name,schedule_limit, max_run_duration from dba_scheduler_jobs where job_name like '%TEST%';
3. Add the run limit clause through PL/SQL block.
begin
SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
( name => 'TEST.TEST'
,attribute => 'MAX_RUN_DURATION'
,value => TO_DSINTERVAL('+000 04:00:00'));
end;
4) Re-run the "select" SQL -> the run total and scheduler limit are all set.
5) Make some changes in Toad for managing the scheduler job (like notification email body or notification destination and the PL/SQL of the actual job command ).
6) Rerun the select statement.
The run limit is now null and the scheduler duration is still set.