Concurrent Request: Inactive phase, No Manager status

Symptom

Submit a request and find that almost all Concurrent managers are in No Manager status, and Phase is Inactive.

Solution

The lifecycle of a Concurrent Request contains different phases (Phase): Pending, Running, and Completed, and may have different States for each Phase.

• Pending Phase-Normal, Standby, Scheduled, Waiting
• Running Phase-Normal, Paused, Resuming, Terminating
• Completed Phase-Normal, Error, Warning, Cancelled, Terminated
• Inactive Phase-Disabled, On Hold, No Manager

For the Concurrent Request of Phase: Inactive, Status: No Manager, you can perform the following checks:

Check whether the FNDLIBR process is started.

FNDLIBR: Concurrent Manager. For details, refer to the ps command in Linux to view Oracle-related processes.

Ps-ef | grep FNDLIBR

FNDLIBR process indicates that concurrent mnagers are up and requests are running on the system. sometimes it happens that even after stopping the concurrent managers by adcmctl. sh stop apps/apps some of the requests might continue running. in such cases you can wait for say 5 minutes and then if it dos not stop then you can kill those FNDLIBR processesKill-9 <processid>

Check whether Concurrent Manager is running

Check MethodSystem Administrator responsibility,Concurrent> manager>Administer. If the Target under Processes is equal to Actual and greater than 0, it means that the manager is started.

1 2 Next Page