Troubleshooting Guide Related To "Failed to start Scheduler XXXXX" Errors in spl_service.log While Scheduler Repeatedly Restarts Causing Unassigned Workorders (Doc ID 1229724.1)

Last updated on MARCH 04, 2024

Applies to:

Oracle Real-Time Scheduler - Version 2.1.0 and later
Oracle Utilities Mobile Workforce Management - Version 2.0 to 2.1.0 [Release 2.0 to 2.1]
Information in this document applies to any platform.

Purpose

This troubleshooting guide outlines steps to determine why an activity is not assigned to shifts and dispatched to the mobile worker. These problems relate to the error stating, "Failed to start Scheduler XXXXX" that appear in the spl_service.log while the scheduler repeatedly restarts as shown in the smauto.YYMMDDxxxx.log. Sample error messages are shown below.

Example I spl_service.log

Troubleshooting Steps

	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

Example I spl_service.log

Example II smauto.YYMMDDxxxx.log

Troubleshooting Steps

1. Is the ENTIRE1 scheduler online (or the problem scheduler) ?

2. Make the following modifications to your default scheduler configuration to increase the logging capabilities of Oracle Realtime Scheduler (ORS). The logs are required by support to troubleshoot problems you report in an SR. In addition, the ORS scheduler will not work without the .map file so a check is included. If these changes/checks do not resolve the issue continue to step 3 below.

3. Enable core dumps and continue to step 4 below.

4. Insure the stack limit is set appropriately.

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