EBS Concurrent Manager (Internal Manager) Does Not Start status shows Actual 1 and Target 0 Processes

In this post we will learn how to  fix "internal manager actual 1 target 0' issue in EBS.

Some time Internal Manager not started properly due to this issue it shows actual 1 and target 0. In this scenario we will learn how to fix this issue.


First of all we need to identify the actual system pid of Internal Manager.




$ps -ef|grep FNDLIBR

applmgr  35531 35526  0 13:02 pts/0    00:00:01 FNDLIBR

or 

click on internal manager and check the process and kill them.

$kill -9 35531 


Start the concurrent manager:-


Source the environment.

$$ADMIN_SCRIPTS_HOME/adcmctl.sh start

$$ADMIN_SCRIPTS_HOME/adcmctl.sh status


No comments:

Post a Comment

Thanks for reading till end. I hope this will help you more to improve your knowledge.

Now it's your turn!

What do you think? Share your experience in the comments box and subscribe for more interesting post.