Re: 'Internal Concurrent Manager status cannot be determined'

Posted by Roshan on Jan 12, 2024; 12:31pm
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/Internal-Concurrent-Manager-status-cannot-be-determined-tp12252p12255.html

Hello,

thanks for the update.

Relink is successful. Manager shows active

ebsdev:/ebs12/inst/apps/EBSDEV_ebsdev/admin/scripts (oraappl) # sh adcmctl.sh status

You are running adcmctl.sh version 120.17.12010000.5


Enter the APPS username : apps

Enter the APPS password :
Internal Concurrent Manager is Active.

adcmctl.sh: exiting with status 0


adcmctl.sh: check the logfile /ebs12/inst/apps/EBSDEV_ebsdev/logs/appl/admin/log/adcmctl.txt for more information ...

ebsdev:/ebs12/inst/apps/EBSDEV_ebsdev/admin/scripts (oraappl) #  ps -ef | grep FNDLIBR
 oraappl 12517666 63635660   0 16:24:13  pts/0  0:00 FNDLIBR                                                                                                
 oraappl 43385100 34079148   2 16:30:31  pts/0  0:00 grep FNDLIBR
ebsdev:/ebs12/inst/apps/EBSDEV_ebsdev/admin/scripts (oraappl) #  ps -ef | grep FNDLIBR
 oraappl 12517666 63635660   0 16:24:13  pts/0  0:00 FNDLIBR                                                                                                
 oraappl 54788462 34079148   2 16:30:33  pts/0  0:00 grep FNDLIBR
ebsdev:/ebs12/inst/apps/EBSDEV_ebsdev/admin/scripts (oraappl) #


But the FNDLIBR processes are not starting.

Regards,
R