Concurrent Request:Inactive phase,No Manager status

Concurrent Request:Inactive phase,No Manager status

Symptom

随便submit一个request，发现几乎所有的Concurrent Manager都为No Manager状态，Phase为Inactive。

Solution

一个Concurrent Request的生命周期包含不同的阶段(Phase)：Pending, Running, and Completed，并且对于每一个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

对于Phase:Inactive,Status:No Manager的Concurrent Request,可以做以下检查

看下FNDLIBR进程是否启动

FNDLIBR:Concurrent Manager 见 Linux下使用ps命令来查看Oracle相关的进程

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 processes bykill -9 <processid>

检查Concurrent Manager是否处于运行状态

检查方法System Administrator responsibility，concurrent > manager > administer,如果Processes下面，Target等于Actual,并且大于0，这就意味着manager是启动的。