Concurrent Processing - Requests Stuck with Inactive No Manager - Routine AFPESA Cannot Construct the Name of an Executable File
(Doc ID 392246.1)
Last updated on AUGUST 11, 2024
Applies to:
Oracle Application Object Library - Version 11.5.0 to 11.5.10.2 [Release 11.5]Oracle Concurrent Processing - Version 11.5.10.0 to 11.5.10.2 [Release 11.5]
Information in this document applies to any platform.
Applications Install 11.5.1 to 11.5.10
Symptoms
All the Concurrent Requests are showing up with Phase Inactive and Status No Manager. The Standard Manager is not able to process any request because each manager process dies immediately after starting up. The log file of the manager process shows the following error:
List of errors encountered:
.............................................................................
_ 1 _
Routine AFPESA cannot construct the name of an executable file for
your concurrent request 2181143.
Check that the file name components are correct and valid on your
system. Check that the environment for the person who started the conc
.............................................................................
The problem typically occurs on a cloned environment that has been created.
Changes
The environment is a cloned one.
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |