EM Jobs Service is down (fatal). Reason - "Reason for delay could not be determined"

Question

Hi all -
I'm having a problem with my em jobs service.  It's listed as down.  Severity is "Fatal".   For the incident creation DATE it has the following:
"Reason for delay could not be established."
Note that it's the DATE column where it ways that the reason could not be established.    Under "message" it has Dec 28, 2013 8:46:29 PM. 
Target Name
Target Type
Severity
Message
Incident Creation Date
Incident Last updated Date
Escalation Level
EM Jobs Service
EM Service
Dec 28, 2013 8:46:29 PM
Reason for delay could not be established.
Jan 27, 2014 7:48:44 PM
None
Does anyone have any clue as to why this is happening and/or how to fix it?
Thanks,
Tom

Answer 1

Hi,
Follow the below steps
1. Click on Repository Database Target in Cloud Control
2. Navigate to : Administration -> "Oracle Scheduler" -> Home -> click on "Oracle Scheduler" it will return, "Scheduler Jobs"
3. Check that the scheduled jobs are running at their correct schedules.  Check if the "EM_JOBS_STEP_SCHED" job is disabled.
4. Select "EM_JOBS_STEP_SCHED" and click on "Edit job Definition" ensure that the job status is "enabled". Then click apply.
5. Check the "EM Jobs Service" status , it should now be shown as UP.
Also
1. Login to 12c Console, Targets --> All Targets --> EM Jobs Service
2, click on Monitoring Configuration tab
3. click on System Configuration
In the Availability Definition screen, under Key Component column, check all the check boxes
4. Similarly, in the System Configuration screen, under Key Component column, check all the check boxes
Wait for 5 minutes and then check the status of the target again.
Regards,
Rahul