ORA-12005: may not schedule automatic refresh for times in the past
2017-08-31 14:52
811 查看
ORA-12012: error on auto execute of job 125
ORA-12005: may not schedule automatic refresh for times in the past
ORA-12012: 自动执行作业 125 出错
ORA-12005: 不能安排过去时间的自动刷新
dba_jobs包含以下几个主要的字段:
(a)LAST_DATE:Date on which this job last successfully executed--job执行成功的时间,即1.job执行成功;2.是job执行完毕的时间
(b)LAST_SEC:同LAST_DATE
(c)THIS_DATE:Date that this job started executing (usually null if not executing)--没有job在执行的时候,该字段为空。若有job正在运行,这个时间是job的开始执行时间。
(d)THIS_SEC:同THIS_DATE
(e)NEXT_DATE:Date that this job will next be executed--job下次执行时间点。
(f)NEXT_SEC:同NEXT_DATE
(g)INTERVAL:A date function, evaluated at the start of execution, becomes next NEXT_DATE--重点的说明一下这个参数,这个参数涉及到next date的计算,next就是根据job的开始执行时间点,结合interval中的时间函数,算出来的。
比如,某个job开始执行时间8月1日23:55,那么如果interval是trunc(sysdate)+1435/1440,因此,next date就是把job的开始时间23:55,代入到interval中的sysdate,得到的结果就仍然是8月1日的23:55。而next date的更新,是一次job完成时更新的,比如job在8月2日的0:15完成,于是在更新next
date的时候,就发现next date的时间晚于当前的时间,于是就报错may not schedule automatic refresh for times in the past。而事实上,job应该是成功执行了的。
为了解决这个报错,interval改成trunc(sysdate+1)+1435/1440。
注意:
如果一个job执行failure后,oracle会尝试重新执行,若16次尝试后还是failure,则oracle会将这个job的broken设为true,即停掉这个job。
当job失败后,系统会在1分钟后重新运行这个JOB,如果还是失败,就在和第1次失败间隔2分钟的时候继续运行这个JOB,如果还是失败,就在和 第2次失败相隔4分钟后运行这个JOB,直到 失败间隔时间≥interval(JOB正常工作的时间设置参数)后,系统检测的时间间隔就为interval.直到第16次失败就会将这个job置为 broken。
--本篇文章转自:http://blog.163.com/ansel_zlh/blog/static/103727172008825113225901/
http://gxg353.blog.sohu.com/236100357.html
http://blog.sina.com.cn/s/blog_60b1f55d01014mje.html
ORA-12005: may not schedule automatic refresh for times in the past
ORA-12012: 自动执行作业 125 出错
ORA-12005: 不能安排过去时间的自动刷新
dba_jobs包含以下几个主要的字段:
(a)LAST_DATE:Date on which this job last successfully executed--job执行成功的时间,即1.job执行成功;2.是job执行完毕的时间
(b)LAST_SEC:同LAST_DATE
(c)THIS_DATE:Date that this job started executing (usually null if not executing)--没有job在执行的时候,该字段为空。若有job正在运行,这个时间是job的开始执行时间。
(d)THIS_SEC:同THIS_DATE
(e)NEXT_DATE:Date that this job will next be executed--job下次执行时间点。
(f)NEXT_SEC:同NEXT_DATE
(g)INTERVAL:A date function, evaluated at the start of execution, becomes next NEXT_DATE--重点的说明一下这个参数,这个参数涉及到next date的计算,next就是根据job的开始执行时间点,结合interval中的时间函数,算出来的。
比如,某个job开始执行时间8月1日23:55,那么如果interval是trunc(sysdate)+1435/1440,因此,next date就是把job的开始时间23:55,代入到interval中的sysdate,得到的结果就仍然是8月1日的23:55。而next date的更新,是一次job完成时更新的,比如job在8月2日的0:15完成,于是在更新next
date的时候,就发现next date的时间晚于当前的时间,于是就报错may not schedule automatic refresh for times in the past。而事实上,job应该是成功执行了的。
为了解决这个报错,interval改成trunc(sysdate+1)+1435/1440。
注意:
如果一个job执行failure后,oracle会尝试重新执行,若16次尝试后还是failure,则oracle会将这个job的broken设为true,即停掉这个job。
当job失败后,系统会在1分钟后重新运行这个JOB,如果还是失败,就在和第1次失败间隔2分钟的时候继续运行这个JOB,如果还是失败,就在和 第2次失败相隔4分钟后运行这个JOB,直到 失败间隔时间≥interval(JOB正常工作的时间设置参数)后,系统检测的时间间隔就为interval.直到第16次失败就会将这个job置为 broken。
--本篇文章转自:http://blog.163.com/ansel_zlh/blog/static/103727172008825113225901/
http://gxg353.blog.sohu.com/236100357.html
http://blog.sina.com.cn/s/blog_60b1f55d01014mje.html
相关文章推荐
- ORA-12005: may not schedule automatic refresh for times in the past
- 解决The current branch is not configured for pull No value for key branch.master.merge found in config
- The method setValue(String) in the type ParamTag is not applicable for the arguments (long)
- .net邮件错误 :The specified string is not in the form required for a subject.
- [Vs Code]Vue工具错误(The Vue Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted.)
- The method setOnClickListener(View.OnClickListener) in the type View is not applicable for the argum
- Node 2478301 does not exist in the cache. It may have been deleted already.
- MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error
- BEA-290074 <Deployment service servlet received file download request for file "security/SerializedSystemIni.dat". The file may exist, but download of this file is not allowed.>
- The current branch is not configured for pull No value for key branch.master.merge found in configur
- Unable to start debugging on the web server. The web server is not configured correctly. See help for common configuration errors. Running the web page outside of the debugger may provide further information.
- 提示错误:The method replace in the type.. is not applicable for the argument......
- 解决The current branch is not configured for pull No value for key branch.master.merge found in config
- 在 Eclipse 中启动 Debug 模式时提示 Can not find a free socket for the debugger in eclipse
- ORA-23421: job number string is not a job in the job queue
- SmtpClient发送邮件遭遇The specified string is not in the form required for a subject.
- The service cannot be activated because it does not support ASP.NET compatibility. ASP.NET compatibility is enabled for this application. Turn off ASP.NET compatibility mode in the web.config or add the AspNetCompatibilityRequirements attribute to the ser
- The current branch is not configured for pull No value for key branch.master.merge found in config
- Dispatch时产生了这个异常:does not contain handler parameter named ‘method’ This may be caused by whitespace in the label text
- ERROR at line 1: ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized view