Concurrent Program Spawns Child That is Going to Inactive No Manager
(Doc ID 1621537.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.
Attempting to submit a concurrent program that spawns a child concurrent program.
The child concurrent goes to inactive status. There is no manager.
Most of these spawned programs complete with Normal status. However, some are ending up with Inactive /No Manager with the following error:
No concurrent manager is defined to process this request
These instances were possibly cloned from an instance that had a problem with the Concurrent Worker Requests view.
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