SMAUTO Process is Left Running Without Secondary Process Due To Batch Lost DB Connection Fixed in MWM/ORS v22.214.171.124.5
(Doc ID 2101577.1)
Last updated on AUGUST 15, 2018
Applies to:Oracle Utilities Mobile Workforce Management - Version 126.96.36.199.0 to 188.8.131.52.5 [Release 2.2]
Oracle Real-Time Scheduler - Version 184.108.40.206.0 to 220.127.116.11.5 [Release 2.2]
Information in this document applies to any platform.
When a cluster of Schedulers boots, the corresponding (timed) batch processes should start up and each one of them should spawn its child SMAUTO process.
However, we found that in certain cases, the batch process boots, then spawns its SMAUTO, but then the batch fails and SMAUTO remains active. When the same batch process is triggered in another cluster member, it triggers another SMAUTO, which leaves the first one unassociated with any batch process.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!