My Oracle Support Banner

DBMS_SCHEDULER: Job Did not Start For Several Minutes, But Is Scheduled For Every 5 Seconds (Doc ID 2370252.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

A frequently executed job failes randomly with 'TIMED OUT (REASON="Recurring job rescheduled after schedule limit exceeded")'.

After that the job don't get started for serveral minutes.

LOG_ID LOG_DATE OWNER JOB_NAME STATUS REQ_START_DATE ACTUAL_START_DATE RUN_DURATION


46571230 16.03.2017 20:53:09,325228 +01:00 TASKPTEL JOB_TASK_HANDLER SUCCEEDED 16.03.2017 20:53:09,000000 +01:00 16.03.2017 20:53:09,049258 +01:00 +00 00:00:00.000000
46571226 16.03.2017 20:53:04,780158 +01:00 TASKPTEL JOB_TASK_HANDLER SUCCEEDED 16.03.2017 20:53:04,000000 +01:00 16.03.2017 20:53:04,188583 +01:00 +00 00:00:00.000000
46571220 16.03.2017 20:53:00,062287 +01:00 TASKPTEL JOB_TASK_HANDLER SUCCEEDED 16.03.2017 20:52:59,000000 +01:00 16.03.2017 20:52:59,789153 +01:00 +00 00:00:00.000000
46571218 16.03.2017 20:52:55,664869 +01:00 TASKPTEL JOB_TASK_HANDLER SUCCEEDED 16.03.2017 20:52:54,000000 +01:00 16.03.2017 20:52:55,387107 +01:00 +00 00:00:00.000000
46570978 16.03.2017 20:29:47,472134 +01:00 TASKPTEL JOB_TASK_HANDLER SUCCEEDED 16.03.2017 20:29:44,000000 +01:00 16.03.2017 20:29:47,195155 +01:00 +00 00:00:00.000000

Seems we are infected by "DBMS_SCHEDULER Delay Between Req_start_date And Actual_start_date (Doc ID 2217732.1)"

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.