Oracle scheduled task failed

If the system data is not updated, check the Oracle scheduled task. It is estimated that the task is not executed.

The next_date is changed to 4000/1/1, and the broken is selected.

Select * From user_jobs: the number of failed tasks of this task reaches 16.

The following causes are found:

When a task fails, the SNP process tries to run the task again in 1 minute. If this operation fails again, the next attempt will take 2 minutes and the next attempt will take 4 minutes. The task queue doubles the Retry Interval every time until it exceeds the normal operation interval. After 16 consecutive failures, the task is marked as broken. without user intervention, the task queue will not be executed repeatedly.

When the next_date parameter of a task is assigned null, the next running time of the task is set to January 1, 4000, that is, the task will never run again. In most cases, this may be a situation we don't want to see. However, if you want to keep the task in the task queue and do not want it to run, setting next_date to NULL is a very simple method.

 

Manually test the scheduled task. The error message is displayed because the IPv6 IP address fails to be inserted and deleted. The scheduled task is restored and re-executed. If the execution is successful, the number of failures is reset to 0.

How to stop a task:

Dbms_job.broken (v_job, true, next_date );//Stop oneJob, v_job can write the job number,ParametersTrueButFalse,Next_date(Stopped at a certain time)Sysdate(Stop immediately ).