IT Tutorial IT Tutorial | Oracle DBA | SQL Server, Goldengate, Exadata, Big Data, Data ScienceTutorial
I will explain What is the Concurrent Manager and How to Start Stop Concurrent Manager in Oracle EBS in this article. Let’s review Concurrent Manager and How to Start Stop Concurrent Manager.
Oracle Concurrent Manager
Oracle E-Business Suite (EBS) allows lots of users to do many jobs or requests at the same time. Concurrent Manager provide in EBS to manage all of these tasks at the same time. The program that each user will run in EBS is called Concurrent Request, and Concurrent Manager is the program that manages these Concurrent Requests.
To connect and access to Concurrent Manager in Oracle EBS, click on System administrator -> Concurrent -> Manager -> Administer tab. If you have solved problems and compatibility with Java, you can open Concurrent manager as follows.
Concurrent Manager and How to Start Stop Concurrent Manager
Any errors or warnings taken in Concurrent Manager are kept under $COMMON_TOP/admin/log/$ CONTEXT_NAME directory. Generally, if Concurrent Manager is running incorrectly, Actual-Targets values are different from each other in Process section on the upper screen. If the Actual and Target values are greater than 0 and equal to each other (1 in the two above values), the Concurrent Manager is running correctly.
If Concurrent Managers are running properly, their Processes are as follows. If any FNDLIBR process is not exist, Concurrent Manager is not running.
[applmgr@ebstest scripts]$ ps -ef |grep FNDLIBR applmgr 15989 15791 0 17:20 ? 00:00:00 FNDLIBR applmgr 15991 15791 0 17:20 ? 00:00:00 FNDLIBR applmgr 15993 15791 0 17:20 ? 00:00:00 FNDLIBR applmgr 16331 15589 0 17:27 pts/0 00:00:00 grep FNDLIBR [applmgr@ebstest scripts]$
Stop Concurrent Manager
When the Concurrent Manager is not running properly or there is a problem, you should restart it. In Oracle EBS, Concurrent Managers are stopped as follows and then started.
[applmgr@ebstest ~]$ cd $ADMIN_SCRIPTS_HOME [applmgr@ebstest scripts]$ sh adcmctl.sh stop You are running adcmctl.sh version 120.19.12020000.7 Enter the APPS username : apps Enter the APPS password : Shutting down concurrent managers for VIS ... ORACLE Password: Submitted request 7465770 for CONCURRENT FND SHUTDOWN adcmctl.sh: exiting with status 0 adcmctl.sh: check the logfile /u01/apps/VIS/fs1/inst/apps/VIS_ebstest/logs/appl/admin/log/adcmctl.txt for more information ... [applmgr@ebstest scripts]$
After execute stop, check the FNDLIBR process as follows, still wait a little bit and ypu will see that they will die. If you don’t want to wait, you can kill the process with kill -9.
[applmgr@ebstest scripts]$ ps -ef | grep FNDLIBR applmgr 1830 1825 0 Jan10 ? 00:12:42 FNDLIBR applmgr 3182 2983 0 Jan10 ? 00:00:33 FNDLIBR applmgr 3212 2983 0 Jan10 ? 00:00:50 FNDLIBR applmgr 3217 2983 0 Jan10 ? 00:00:50 FNDLIBR applmgr 3275 2983 0 Jan10 ? 00:00:00 FNDLIBR applmgr 18848 18393 0 08:32 pts/0 00:00:00 grep FNDLIBR [applmgr@ebstest scripts]$ [applmgr@ebstest scripts]$ [applmgr@ebstest scripts]$ ps -ef | grep FNDLIBR applmgr 19145 18393 0 09:04 pts/0 00:00:00 grep FNDLIBR You have new mail in /var/spool/mail/applmgr
Start Concurrent Manager
Once Stop is completed properly, you can start it like following.
[applmgr@ebstest scripts]$ sh adcmctl.sh start You are running adcmctl.sh version 120.19.12020000.7 Enter the APPS username : apps Enter the APPS password : Starting concurrent manager for VIS ... Starting VIS_0214@VIS Internal Concurrent Manager Default printer is noprint adcmctl.sh: exiting with status 0 adcmctl.sh: check the logfile /u01/apps/VIS/fs1/inst/apps/VIS_ebstest/logs/appl/admin/log/adcmctl.txt for more information ... [applmgr@ebstest scripts]$
Check the FNDLIBR processes again after the start, you can see that FNDLIBR processes are running.
[applmgr@ebstest scripts]$ ps -ef | grep FNDLIBR applmgr 19304 19299 0 09:06 pts/0 00:00:00 FNDLIBR applmgr 19308 18393 0 09:06 pts/0 00:00:00 grep FNDLIBR [applmgr@ebstest scripts]$
Internal manager is alredy down because of some issue. but now i have to make complete application bounce. but am not able to bring standard and other custom managers as IM is down. SO can you please guide me is there any way to bring all managers down
stop all concurrent manager process by using sh adcmctl.sh stop command one or more times. You can also kill the related os process by using kill command.