Scheduler Is Crashing When Stops That Are Not Found Internally Gets Auto UnDispatch
(Doc ID 2261432.1)
Last updated on MARCH 12, 2019
Applies to:Oracle Utilities Mobile Workforce Management - Version 126.96.36.199.13 and later
Oracle Real-Time Scheduler - Version 188.8.131.52.13 and later
Information in this document applies to any platform.
The scheduler is not running and crashes. Upon further review, a core dump was produced. A submit job for the scheduler immediately follows the core dump, but the scheduler did not start. The following error is seen in the scheduler logs:
shift<28077261587727>: target<SHIFT <57784592298576>> costs (u-r+i=ttl) 500 - 42334 + 24238.1 = -17595.9
SCH066 05/04/17 09:43:53.089 [293:43:06.700] AutoUnDispatch: test undispatch group<55090096380307> from
shift<28077261587727>: target<SHIFT <57784592298576>> costs (u-r+i=ttl) 300 - 37804.4 + 19081.5 = -18422.9
SCH066 05/04/17 09:43:53.100 [293:43:06.710] Caught signal 11
SCH066 05/04/17 09:43:53.100 [293:43:06.710] Segmentation fault
SCH066 05/04/17 09:43:53.100 [293:43:06.710] Attempting to flush all open files
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!