'Internal Concurrent Manager status cannot be determined'

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

'Internal Concurrent Manager status cannot be determined'

Roshan
EBS 12.1.3
Hello Erman,

FNDLIBR processes are not showing when starting concurrent manager. Status shows
Internal Concurrent Manager status cannot be determined

Kindly advise.

you may be missing some files for product "=y",
or "=y" could be an invalid product.

adrelink will not try to link product "=y".
Continuing work on other products...

adrelink: error: Product library for product "ranlib" not found.
"ranlib" might not be listed correctly in your EBSDEV_ebsdev.env file,
you may be missing some files for product "ranlib",
or "ranlib" could be an invalid product.

adrelink will not try to link product "ranlib".
Continuing work on other products...

Starting  link of product 'inv' on Thu Jan 11 14:04:02 WST 2024
Current product is  inv
Current product _TOP is  $INV_TOP
Current prodarea is  /ebs12/apps/apps_st/appl/inv/12.0.0

Backing up or removing executables...

Adrelink is failing
https://community.oracle.com/mosc/discussion/3007777/concurrent-managers-actual-not-matching-target-processes

Kindly advise.

Regards,

Roshan
Reply | Threaded
Open this post in threaded view
|

Re: 'Internal Concurrent Manager status cannot be determined'

ErmanArslansOracleBlog
Administrator
ICM log would be helpful , but instead you are mentioning a relink error.

that ranlib error is weird. That is not a binary or a product.. So probably, you gave some wrong inputs to the relink program. Try relinking without it -> Ex: adrelink.sh force=y link_debug=y "fnd FNDLIBR"

Or use adadmin and specifically make it compile the FNDLIBR.. (I suppose you already know how to use adadmin for  Relinking specific Applications programs..)

Ensure your environment is correct and proper for relinking.
Reply | Threaded
Open this post in threaded view
|

Re: 'Internal Concurrent Manager status cannot be determined'

Roshan
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
Reply | Threaded
Open this post in threaded view
|

Re: 'Internal Concurrent Manager status cannot be determined'

Roshan
This post was updated on .
logs showing these errors


                   Process monitor session started : 12-JAN-2024 16:32:45
CONC-SM TNS FAIL
Call to PingProcess failed for FNDCPGSC
CONC-SM TNS FAIL
Call to StopProcess failed for FNDCPGSC
CONC-SM TNS FAIL
Call to PingProcess failed for FNDCPGSC
CONC-SM TNS FAIL
Call to StopProcess failed for FNDCPGSC
CONC-SM TNS FAIL
Call to PingProcess failed for FNDCPGSC
CONC-SM TNS FAIL
Call to StopProcess failed for FNDCPGSC
CONC-SM TNS FAIL
Call to PingProcess failed for FNDOPP
CONC-SM TNS FAIL
Call to StopProcess failed for FNDOPP
CONC-SM TNS FAIL
Call to PingProcess failed for FNDOPP
CONC-SM TNS FAIL

sysadmin login also is very slow
Reply | Threaded
Open this post in threaded view
|

Re: 'Internal Concurrent Manager status cannot be determined'

Roshan
shall I run autoconfig?
Reply | Threaded
Open this post in threaded view
|

Re: 'Internal Concurrent Manager status cannot be determined'

ErmanArslansOracleBlog
Administrator
Please go through the MOS document : Concurrent Processing - Internal Concurrent Manager ICM log file shows 'CONC-SM TNS FAIL', 'Call to PingProcess failed', and/or 'Call to StopProcess failed' for FNDCPGSC/FNDOPP (Doc ID 1312632.1)
Reply | Threaded
Open this post in threaded view
|

Re: 'Internal Concurrent Manager status cannot be determined'

Roshan
Thanks a lot. Internal Manager issue resolved.