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是啟動的。

1 2 下一頁