Ora-12005:may not schedule automatic refresh for times in the past

Source: Internet
Author: User

Ora-12012:error on Auto execute of Job 125

Ora-12005:may not schedule automatic refresh for times in the past

ORA-12012: Auto-Perform job 125 error

ORA-12005: Cannot schedule automatic refresh of past time


Dba_jobs contains the following key fields:

(a) Last_date:date on which the last successfully executed--job performed successfully, that is, 1.job execution succeeded; 2. The time the job was executed
(b) Last_sec: Tong Last_date
(c) This_date:date This job started executing (usually null if not executing)-the field is empty when no job is executing. If a job is running, this time is the start of the job execution time.
(d) This_sec: Same this_date
(e) Next_date:date This job would next be executed--job the next execution point in time.
(f) next_sec: Tong Next_date
(g) Interval:a date function, evaluated at the start of execution, becomes next next_date--focuses on this parameter, which involves the calculation of next date, Next is based on the start of the job execution point in time, combined with the time function in interval, calculated.

For example, if a job begins execution time August 1 23:55, then if interval is trunc (sysdate) +1435/1440, then next date is the start of the job 23:55, into interval , the result is still 23:55 of August 1. The update for next date, which is updated when a job completes, such as when the job completes at 0:15 on August 2, and then updates next date, discovers that next date is later than the current time, and the error may be not schedule Automatic refresh for times in the past. In fact, the job should have been executed successfully.

In order to solve this error, interval changed to Trunc (sysdate+1) +1435/1440.

Attention:

If a job executes failure, Oracle tries to do it again, and if it is failure after 16 attempts, Oracle sets the job's broken to true, stopping the job.
When the job fails, the system will rerun the job after 1 minutes, and if it fails, continue to run the job 2 minutes after the 1th failure, and if it fails, run the job after 4 minutes apart from the 2nd failure until After the failure interval ≥interval (setting parameters for the job's normal working time), the system detects an interval of interval. The job is set to broken until the 16th failure.

--This article from: 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

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.