Last updated on APRIL 09, 2012
Applies to:Oracle Utilities Mobile Workforce Management - Version: 2.1.0
Information in this document applies to any platform.
A batch job set to run once per day, submits jobs continuously as if there is no Timer Interval configured. The only way to stop the batch from running is to kill the threadpool worker process. You can’t deactivate it from the batch control because it is updating too frequently and you always get “updated by another user” errors if you try to update the control.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms