Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve got a dbms_scheduler-Job running in Oracle 10.2.0.
When I change the system date back to yesterday, the job will wait for one day to continue its work. The reason for this is that next_run_date does not change.
This does not happen regularly, but sometimes someone decides to change the system date without thinking or even knowing about oracle jobs running.
Any suggestions on how to keep my job running with the configured interval (without having it to change manually)?
If you are changing the system date out from underneath Oracle, your hands might be tied. Is there a reason you are regularly changing the system date? If so, perhaps you should create a script for doing so, and have that script also update next_run_date.