How to clean Concurrent Managers Nodes on Cloned instances.

Hi,
We have PCP on PROD environment, when we do cloning to test instances, after running exec FIND_CONC_CLONES on test instances , TEST instance concurrent managers nodes are still pointing to PROD CM nodes, Please let me know how to change to test concurrent manager nodes, I know we can do it manually its all time taken process to change all managers one by one.
Thanks

Hi;
Please check below thread;
Re: Standard Manager still pointing to PROD after Clone
EXEC FND_CONC_CLONE.SETUP_CLEAN;
If its not help please update thread

Similar Messages

How to migrate the concurrent managers definations from one instance to another

How to migrate the concurrent managers definitions from one instance to another instance by using FNDLOAD in R12.1.3
Greatly appreciate any help on this.
Thanks!

Concurrent managers can't be migrated using FNDLOAD -- Tips and Examples Using FNDLOAD (Doc ID 735338.1)
What are you trying to achieve here? Why migrating CMs from one node to another?
Thanks,
Hussein

Concurrent Managers on Multiple nodes

Hi,
We have this setup
2 DB server - RAC & ASM
2 APPS server - which has loand balancing through IP configuration.
Now we have requirement of having concurrent managers in the DB server. I am bit confused here
1) suppose if i install cm tier on both DB servers and ask them to communicate to RAC DB server, IF any request comes , how this will distribute the work between two servers.
2) do we have to configure anything ?
3) Is there any entry is available in config files with respect to CONCURRENT HOST NAME. How the values are populating in FND_NODES table.
4) am i thinking two complex, is there any other solution to achiev this - Basically i have to have concurrent manager in both DB server and work needs to be shared automatically.
Waiting for your valuable inputs.
Cheers!
Venki.

Forgive my brief answers; I'm headed to bed and don't have time to dig up full references. :-)
As a side note, in the future, please start a separate thread. Your environment and requirements are different from the original poster, and replies may be confusing, both to future readers, and to those trying to help.
1) Is it possible to configure PCP keeping both the CM on appsTier in non-RAC env. ?Yes.
2) If yes, will both the CM work at the same time or one at a time? In other words, it can distribute the CM load among the CM tiers?All the CMs will run at the same time, managed by ICM and GSM.
3) If yes, please provide me a guideline or any special instruction.You note below that you won't be using a shared application tier filesystem. You might want to reconsider this architecture. At the very least, you will want to share the log and output directories for the concurrent managers. Life will be much easier if all nodes can see the same log and output files. :)
Take a look at section 3.12 of
Note 388577.1: Using Oracle 10g Release 2 Real Application Clusters and Automatic Storage Management with Oracle E-Business Suite Release 12. Although you're not running RAC, this section of the document explains the various parameters needed to configure PCP.
Also, if you haven't already, review the sections on PCP in the Oracle E-Business Suite System Administrator's Guide - Configuration
Since, I'm planning to go with 2 appsTier nodes (non-shared, local filesystem), I would like to go for LoadBalancing configuration as well.
Refered Note: 380489.1 - Using Load-Balancers with Oracle E-Business Suite Release 12
Section 2.4 Using Domain Name Server (DNS) Load Balancing with Single Web Entry Point
Is the above DNS Load Balancing is only for web services? what about other services (forms,CM)? Should work for Forms as well. CMs mostly care about where the database is, not the web/forms entry point, so the Load Balancer doesn't come into play for the CMs ...at least, I'm pretty sure that's true. It's late. :)
Once LoadBalancing is done, then is it possible to go for E-Biz integration with OID/SSO?Yes. See Integrating Oracle E-Business Suite Release 12 with 10g AS Oracle Internet Directory and Oracle Single Sign-On
Regards,
John P.
http://only4left.jpiwowar.com

Two node installation with 2 concurrent managers..

Need your help. I have 12.1.1 Two node installation on Linux 5.9 with 64 bit.
Linux2- Database server + Concurrent manager
Linux1- Apps Node
Port - 8002 (port pool -2)
on my app node - linux1, I have 2 directories <SID>_linux1 and <SID>_linux2. First one is for primary apps node and second one is for 2nd concurrent manager. It is a shared directory structure. I have 2 questions:
1) If I run the autoconfig on Linux1, I can run all the services and connect to apache. However, If I run the autconfig on linux2, I will not be able to connect to web server (for a short time request will be sent to Linux1 and then it gets forwarded to Linux2 - even though Linux2 is not app server).
2) How do I run the second concurrent manager on LInux2? After I run the 2 concurrent manager, how do I test both concurrent managers are working?
Your help is much appreciated.

Hi Hussein,
Thank you for the info. I was wondering whether the Linux2 concurrent manager was installed correctly or not. I went to xml file and found these entries and it made me think, it didn't install correctly because only concurrent manager should have been yes and the rest should be no. Isn't it? If it is wrong, how do I correct this?
<oa_system_config>
         <TIER_DB oa_var="s_isDB">NO</TIER_DB>
         <TIER_ADMIN oa_var="s_isAdmin">YES</TIER_ADMIN>
         <TIER_WEB oa_var="s_isWeb">YES</TIER_WEB>
         <TIER_FORMS oa_var="s_isForms">YES</TIER_FORMS>
         <TIER_NODE oa_var="s_isConc">YES</TIER_NODE>
         <TIER_FORMSDEV oa_var="s_isFormsDev">YES</TIER_FORMSDEV>
         <TIER_NODEDEV oa_var="s_isConcDev">YES</TIER_NODEDEV>
         <TIER_WEBDEV oa_var="s_isWebDev">YES</TIER_WEBDEV>
         <config_option type="techstack" oa_var="s_techstack">as1013</config_option>
         <config_option type="techstack" oa_var="s_tnsmode">generateTNS</config_option>
         <config_option type="adx" oa_var="s_apps_version">12.1.1</config_option>
         <config_option type="techstack" oa_var="s_apache_mode">NORMAL</config_option>
         <ias_version oa_var="s_ias_version">10.1.3.4.0</ias_version>
      </oa_system_config>

After Cloning Concurrent managers erroring out while coming up

Hi
I have cloned the r12.1.1 instance all the things are successful but the concurrent managers are not coming up.
I checked the by login as sysadmin concurrent-->administer-->select standard manager-->processes log file i found the following errors
Application Object Library: Concurrent Processing version 11.5
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
STANDARD Concurrent Manager started : 05-OCT-2011 13:33:49
05-OCT-2011 13:33:49
Starting concurrent program FNDWFBG for concurrent request 19347388 (MODULE=FNDWFBG)
05-OCT-2011 13:33:50
Starting concurrent program FNDWFBG for concurrent request 19347390 (MODULE=FNDWFBG)
Routine AFPCSQ encountered an ORACLE error. ORA-12170: TNS:Connect timeout occurred
Review your error messages for the cause of the error. (=<POINTER>)
Shutting down Concurrent Manager : 05-OCT-2011 13:37:04
ORA-01012: not logged on
ORACLE error 3114 in AFPRSR-Resubmit_Time
Cause: AFPRSR-Resubmit_Time failed due to ORA-03114: not connected to ORACLE
The SQL statement being executed at the time of the error was: and was executed from the file .
List of errors encountered:
_ 1 _
Routine AFPCMT encountered an ORACLE error. ORA-01012: not logged on.
Review your error messages for the cause of the error. (=<POINTER>)
_ 2 _
Routine AFPPRD has encountered a fatal error. ORA-03114: not connected
to ORACLE
Contact your system administrator or support representative.
_ 3 _
Routine AFPCSQ encountered an ORACLE error. ORA-12170: TNS:Connect
timeout occurred
Review your error messages for the cause of the error. (=<POINTER>)
I tried to trouble shoot the issue by doing the following things
1)stop all Appl services
2)stop database and listener
3)start db and listener
4)as a apps user
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
5)run Auotconfig on DB Tier
6)as a apps user execute the following script
SQL> @$FND_TOP/patch/115/sqlafdcm037.sql;
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';
7)ran adrelink for FND module
Go to cd $FND_TOP/bin
$ adrelink.sh force=y "fnd FNDLIBR"
$ adrelink.sh force=y "fnd FNDSM"
$ adrelink.sh force=y "fnd FNDFS"
$ adrelink.sh force=y "fnd FNDCRM"
8)run autoconfig on appl tier
9)run cmclean.sql
10) start all the application services.
All went fine but the concurrent manager are terminating with the error messages above....
Please can any one help on this....
Thanks
SAI

Hi,
I think it is the issue with standard manager. during startup of application triger to intialize standard manager service is not working fine.
Execute the following to alter trigger FNDSM:
CREATE OR REPLACE TRIGGER fndsm
AFTER INSERT OR UPDATE ON FND_NODES
FOR EACH ROW
BEGIN
if ( :new.NODE_NAME <> 'AUTHENTICATION' ) then
if ( (:new.SUPPORT_CP='Y')
or (:new.SUPPORT_FORMS='Y')
or (:new.SUPPORT_WEB='Y') ) then
fnd_cp_fndsm.register_fndsm_fcq(:new.NODE_NAME);
end if;
if (:new.SUPPORT_CP = 'Y') then
fnd_cp_fndsm.register_fndim_fcq(:new.NODE_NAME);
end if;
end if;
END;
commit;
Clean FND_NODES by executing the following:
exec FND_CONC_CLONE.SETUP_CLEAN;
Run autoconfig.
Restart concurrent managers and retest.
Hope this may help...!!!
Regards RanjanS

How to assign particular concurrent requests to sparate concurrent managers

How to assign particular Users concurrent requests to custom or Sparate concurrent managers
OS : Linux
Apps: 11.5.10.2

Hi,
This can be done via "Specialization Rules".
How to Create a Custom Concurrent Manager [ID 170524.1
How to Split the Load of Work to Many Concurent Managers [ID 473310.1]
Oracle Applications System Administrator's Guide - Configuration (zipped) -- Page 7-14
http://download.oracle.com/docs/cd/B25516_18/current/acrobat/115sacg.zip
Make sure you bounce the CM once you are done.
Thanks,
Hussein

Target node/queue unavailable for 12i Concurrent Managers on Redhat Linux

Hi,
I was able to sucessfully install Release 12 Vision on Redhat Linux.. Every thing is working fine but concurrent managers are not active except the Internal Manager. Rest of the Managers has no value in the node name field and the status is "Target node/queue unavailable".. I also ran adcmcmtl.sh to manually stop and start the managers but still facing the same issue..
Please tell me what i'm missing..
Thanks in Advance,
Prasad

Duplicate post ..
Re: Not able to start the concurrent Managers in Release 12 on Redhat Linux 4
I suggest we follow up on one post so we can get more input from others.

R12 Concurrent managers + forms on a single node?

He friends
I wanted to have your views on the following topic.
Currently I have an 11.5.10 Apps setup on 2 different nodes.One hosting forms + apache and second one hosting DB and Concurrent managers.
Now I am moving on R12 on new poweful servers both for apps and Db.
My team is planning to have the concurrent managers+ forms ..in fact all services inclusive of discoverer on one node and only DB on the second node.
Kindly provide your views.
Kam.

My team is planning to have the concurrent managers+ forms ..in fact all services inclusive of discoverer on one node and only DB on the second node.
Kindly provide your views.This should be OK as long as you have sufficient resources on that node.
Thanks,
Hussein

How often to bounce Concurrent Managers

We're running a High-Availability environment with 11i on HP-UX 64-bit. How often should the concurrent managers be bounced? Oracle tech support periodically suggests bouncing the concurrent managers to resolve some of our TARs. If bouncing needs to occur daily or weekly, what's the reason? To clear the cache? If so, where is this cache in the SGA?
thanks,
Kraig Hotelling - Apps DBA

hsawwan wrote:
Hi,
Please see "Oracle Self-Service Human Resouces Deploy Self-Service Capability Guide" manual, Page 4-12 -- Running the Workflow Cleanup Process.
Oracle Self-Service Human Resouces Deploy Self-Service Capability Guide
http://download.oracle.com/docs/cd/B53825_03/current/acrobat/121sshrig.pdf
Thanks,
HusseinThanks again Hussein.
Actually, from the document above, it seems the correct order is the other way round to what I posted.
Before you run the cleanup process, you must define a request set that runs the Purge
Obsolete Workflow Runtime Data (FNDWFPR) concurrent program before the
Complete Defunct HR Workflow Resources (HRWFDFCT) concurrent program.Regards

All Concurrent managers going down (Except Internal conc manager)

Hi All,
We are on Oracle Apps R12.0.4 and Db 10g
We have done a cloning from RAC ASM 2 node instance to Non-RAC NonASM single node.
The problem is that concurrent managers (Standard manager and other manangers) are going down automatically.
ICm obviously is trying to bring them back .
here is the log file:
Starting INVMGR Concurrent Manager : 29-JUN-2010 07:49:18
Process monitor session ended : 29-JUN-2010 07:49:18
Process monitor session started : 29-JUN-2010 07:51:18
Adding Node:(APP2), to unavailable list
Found dead process: spid=(28003), cpid=(240974), ORA pid=(44), manager=(0/4)
Found dead process: spid=(28002), cpid=(240973), ORA pid=(43), manager=(0/5)
Starting FNDSCH Concurrent Manager : 29-JUN-2010 07:51:18
Starting FNDCRM Concurrent Manager : 29-JUN-2010 07:51:18
Starting OAMCOLMGR Concurrent Manager : 29-JUN-2010 07:51:18
Starting FTE_TXN_MANAGER Concurrent Manager : 29-JUN-2010 07:51:18
Starting IEU_SH_CS Concurrent Manager : 29-JUN-2010 07:51:18
Starting IEU_WL_CS Concurrent Manager : 29-JUN-2010 07:51:18
Starting PASMGR Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting INVMGR Concurrent Manager : 29-JUN-2010 07:51:18
Process monitor session ended : 29-JUN-2010 07:51:18
+++++++++++++++++++++++++++++++++++++++++
What i wanted to know is "Adding Node:(APP2), to unavailable list"
What does this mean and how to troubleshoot it ?
Also, i can see that STATUS column in FND_NODE table is set to "N"
Does it mean something which affects the concurrent managers?
Please help me resolve this.
Thanks,
KK

Hi,
The problem is that concurrent managers (Standard manager and other manangers) are going down automatically.
ICm obviously is trying to bring them back .Please verify the definition of the CMs and make sure none points to the RAC instances.
I would suggest you stop the CM, purge FND_NODES table and run AutoConfig on the database/application tier nodes, run cmclean.sql script, then start the CM and see if you can reproduce the issue.
Thanks,
Hussein

Concurrent Manager Node Name Issue

Hi All,
Recently one of EBS 11i (11.5.10.2 + RHEL 4.7) Node (VM Node) has been cloned to another node. So i had to change the Host name for the cloned application. I followed the meta link note 338003.1 and 341322.1. I am successfully changed the host name and able to access the application as well. When i check the Concurrent manager process's status, its showing Actual-1 and Target -1. B*ut the problem is some of process's node name is showing the previous node name (the name of the node from where cloned).* For example Output Post Processor's node name is showing the previous one and its status showing Actual - 0 and Target - 1. Please let me know why this has happened and also how can i solve this issue?
Thanks,
Mani

Please run cmclean.sql script as per (Concurrent Processing - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]) and check then.
If you still have the same issue, update FND_CONCURRENT_QUEUES table (TARGET_NODE column) -- Troubleshooting the "Error Occurred While Attempting to Establish an Applications File Server Connection" [ID 117012.1]
Please also see (Concurrent Processing - CCM.sql Diagnostic Script to Diagnose Common Concurrent Manager Issues [ID 171855.1]).
Thanks,
Hussein

Erratic behaviour of Concurrent Managers

We have PCP configured on 2 node EBS. We have recently started seeing that our FNDSM on node 2 stops working and also couple of other managers got deativated. When we try to start them manually they won't start. The only thing we do is to bounce application services as pointed out in "Note ID 245563.1 Concurrent Processing - The Concurrent Manager Fails to Start on GSM Enabled Due to DBMS_LOCK.Request ResultCall Failed to Establish ICM" which is not always possible in production:
ICM log file showed:
Routine &ROUTINE has attempted to start the internal concurrent manager. The ICM is already running. Contact you system administrator for further assistance.afpdlrq received an unsuccessful result from PL/SQL procedure or function FND_DCP.Request_Session_Lock.
Routine FND_DCP.REQUEST_SESSION_LOCK received a result code of 1 from the call to DBMS_LOCK.Request.
Possible DBMS_LOCK.Request resultCall to establish_icm failed
The Internal Concurrent Manager has encountered an error.
I went through the note: Concurrent Managers Will Only Start on One Node in PCP/RAC Environment (Doc ID 264296.1)
So I have questions regarding this:
1. Does ICM runs only on primary node as I believe?
2. When starting the application we start the node 1 and then node 2 by using adstartal.sh which internally executes adcmctl.sh on both the nodes, as the note points out we should run adcmctl.sh only from primary node. How to solve this problem?
3. If this issue is common how should we start application on another node and still not execute adcmctl.sh?

1. Does ICM runs only on primary node as I believe?You can setup the internal manager on both nodes but it will start (be running) on one node only.
How to Setup and Test Failover of PCP on Non-RAC Environments. [ID 743716.1]
Can a Concurrent Manager Tier be Added Without Setting Up PCP? [ID 389876.1]
2. When starting the application we start the node 1 and then node 2 by using adstartal.sh which internally executes adcmctl.sh on both the nodes, as the note points out we should run adcmctl.sh only from primary node. How to solve this problem?You can start adcmctl.sh on both nodes so you use adstrtal.sh on both nodes and the internal manager will be running on one node only.
3. If this issue is common how should we start application on another node and still not execute adcmctl.sh?I have already answered this above.
Thanks,
Hussein

Not able to start the concurrent Managers in Release 12 on Redhat Linux 4

Hi,
I was able to successfully install Release 12 Vision on Other than Linux.. Every thing is working fine but concurrent managers are not active except the Internal Manager. Rest of the Managers has no value in the node name field and the status is "Target node/queue unavailable".. I also ran adcmcmtl.sh to manually stop and start the managers but still facing the same issue.. Other than the install, i have not applied any patches..
Please tell me what i'm missing..
Thanks in Advance,
Prasad

Check the CM log file for any errors.
Have you tried to recover the CM from OAM? Shutdown the CM first and run this step.

V$license and concurrent managers

Are concurrent managers considered part of session limits in terms of licensing. In other words, do they count as sessions towards license limits?
Thanks.

Hi,
Please find these docs
Concurrent Managers Fail To Start After New Install of Release 12 (Doc ID 413164.1)
ICM Not Starting: Node Name not Registered (Doc ID 602942.1)
Regards
Yoonas

Concurrent managers ( JVM)

I have a R12 Vision environment installed on Solaris 5.10 on 2 nodes, with batch processing ( and database) on one node ( Node A), and rest of the apps tier services running on the second node ( Node B).
What I wanted to find out was the memory requirement for this environment. The purpose is to use this to get a better idea of the hardware requirement for 10 instances of Oracle Applications which we need to create as part of a fresh implementation.
So, I thought, I'll check the default sizes needed for running
a) database
b) applications
a) database part I've taken care of
b) applications:
On node B ( web / forms tier)
First I wanted to check the default sizes of all the JVMs installed.
I understand that on the 3 of the JVMs start up with the following default max heap size
FORMS JVM
-Xmx256M
OACORE JVM
-Xmx512M
OAFM JVM
-Xmx256M
On Node A ( concurrent processing )
When I do a
ps -ef |grep applmgr |grep -i DCLIENT
I see some 12 processes for these
applmgr 3701 3637 0 Sep 10 ? 7:52 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
applmgr 3703 3637 0 Sep 10 ? 8:23 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
applmgr 3695 3637 0 Sep 10 ? 17:28 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
applmgr 3699 3637 0 Sep 10 ? 8:17 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
applmgr 3694 3637 0 Sep 10 ? 8:21 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
applmgr 3697 3637 0 Sep 10 ? 16:05 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
applmgr 3696 3637 0 Sep 10 ? 16:43 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
applmgr 3700 3637 0 Sep 10 ? 8:17 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
applmgr 3698 3637 0 Sep 10 ? 7:46 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
applmgr 3704 3637 0 Sep 10 ? 10:06 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
applmgr 3705 3637 0 Sep 10 ? 8:14 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
applmgr 3706 3637 0 Sep 10 ? 8:18 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
All of these have the parent process id as 3637, which is the process for the service manager ( FNDSM)
ptre 3637
3637 FNDSM
3673 RCVOLTM APPS/ZGA5A000CCA376B92E66589EB9B640008522DC5AB54ED497EBE6F1E7A2ED33AB28
3674 RCVOLTM APPS/ZG72B4C04ED1376DF24AEB2C215881578D8D686F4949F8BBDF82CACEC6CAA4C430
3675 POXCON APPS/ZGBEBFD251987E7FDC7DAE7D07CBEAE239F56E3DEB751B28748B9B3054CA3BFFAD3
3676 CYQLIB APPS/ZG779BC67A13CBACE567402671E31D0E0282FD0041A8E62272F6A82484551509A09
3677 INCTM APPS/ZGC797A91F15553AC4DC6E7789E860FED9F169749E2D2105716F18C876041CF17AEF
3694 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
3695 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
3696 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
3697 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
3698 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
3699 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
3700 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
3701 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
3702 /u03/oracle/VIS/apps/apps_st/appl/xdp/12.0.0/bin/XDPCTRLS APPS/ZG0D1E37E24F57F5
3703 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
3704 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
3705 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
3706 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
3709 FNDCRM APPS/ZGC0523DAB50578CE9E103ACBB0BCABC57132ECA88FB1B92855FCFFDACE64E9CEF9
3710 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG58C402AF965363D362B15E3D
3711 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG3A071441461117B4AB0C1148
3712 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGCAC037E40629DC25B6A64439
3713 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG7C22F67D5B10AE3786CF3C58
3714 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG7C22F67D5B10AE3786CF3C58
3715 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG7C22F67D5B10AE3786CF3C58
3716 PALIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG56731173E63F582D799ECCE8F
3717 INVLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG5897C948C8DFB32F39009E03
3719 MRCLIB FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG0004527A8F95E64C57A399EA0
What I'm trying to understand is are these many JVMs being spawned by concurrent managers?
If yes, where exactly do I look for to see their JVM sizes?
When I do a top and check the memory of these java processes, each of them seem to be using 211M each ( approx). I would want some control on this. Possibly shutdown the managers which are not needed.
If anyone can throw some light on this concurrent managers and JVMs relationship, it'll be much helpul.

Pretty much every Concurrent Manager known to man is started out of the box in R12. You have to decide what Concurrent Managers can be safely disabled based on what products/modules are in use. You only have to have Internal Manager, Conflict Resolution Manager, Service Managers and Standard Manager. Deactivating the SFM% managers and Workflow Managers will save a ton java resources. Workflow will require the Workflow Agent Listeners to be up. You can stop the Workflow Service Components in Oracle Applications Manager for products you are not using (ECX% for example). These will each spawn a seperate java process.

How to clean Concurrent Managers Nodes on Cloned instances.

Similar Messages

Maybe you are looking for