Shifting of Oracle DBMS Job ScheduleTime

A daily job was scheduled to execute on top of the hour, but by the end of the week, was starting 6 seconds later. Leaving it for a few more weeks, it was by a minute.

Found out it was because of the interval value set as 'SYSDATE+1', making it go slower and slower as the job started later by a few seconds everyday. Adjusting the interval was able to fix it.


- Moving the hour part outside of day calculation:
                  


- Truncating up to the minute to lose seconds: