How to resolve a [COULD NOT START SCHEDULER] alert

Clarity sends a [COULD NOT START SCHEDULER] email alert when communication drops between the Enterprise Server and database. Follow these steps to help restore the connection.

An email alert from Clarity includes the metric, the threshold hit, and the related server. With this information, you can log in to Server Manager and go right to the correct E1 Enterprise Server instance.   

  1. Log in to Server Manager and click the Enterprise Server.
  2. Review the Scheduler kernel logs for more information.
  3. Typically, you can log in to a fat client and restart the Scheduler.
  4. If the Scheduler does not restart, check out Doc ID 1353038.1 at My Oracle Support for troubleshooting tips.