Oracle concurrent managers setup recommendations

Hi,
just wondering if there is a white paper with oracle's recommendations about the number and types of concurrent managers that should be set up.
thanks in advance,
jill

Looks like your fnd_concurrent_processes and fnd_concurrent_requests tables need to be cleaned. Please refer to Note: 134007.1 - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=134007.1

Similar Messages

Oracle E-Biz 12.1.3 - concurrent managers using SFTP

Hi all
Does anyone out there have any knowledge / advice on using Concurrent Managers and SFTP so that output files can be immediately transferred to an external customer?
Kind of wanting by pass the SFTP server.
I cannot find any notes on there so thought I would ask here.
Thanks

953001 wrote:
Hi all
Does anyone out there have any knowledge / advice on using Concurrent Managers and SFTP so that output files can be immediately transferred to an external customer?
Kind of wanting by pass the SFTP server.
I cannot find any notes on there so thought I would ask here.
ThanksPlease see old threads for the same topic/discussion.
https://forums.oracle.com/forums/search.jspa?threadID=&q=FTP+AND+Concurrent&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
https://forums.oracle.com/forums/search.jspa?threadID=&q=SFTP+AND+Concurrent&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks,
Hussein

CONCURRENT MANAGER SETUP AND CONFIGURATION REQUIREMENTS IN AN 11I RAC ENVIR

제품 : AOL
작성날짜 : 2004-05-13
PURPOSE
RAC-PCP 구성에 대한 Setup 사항을 기술한 문서입니다.
PCP 구현은 CM의 workload 분산, Failover등을 목적으로 합니다.
Explanation
Failure sceniro 는 다음 3가지로 구분해 볼수 있습니다.
1. The database instance that supports the CP, Applications, and Middle-Tier
processes such as Forms, or iAS can fail.
2. The Database node server that supports the CP, Applications, and Middle-
Tier processes such as Forms, or iAS can fail.
3. The Applications/Middle-Tier server that supports the CP (and Applications)
base can fail.
아래부분은 CM,AP 구성과
CM과 GSM(Global Service Management)과의 관계를 설명하고 있습니다.
The concurrent processing tier can reside on either the Applications, Middle-
Tier, or Database Tier nodes. In a single tier configuration, non PCP
environment, a node failure will impact Concurrent Processing operations do to
any of these failure conditions. In a multi-node configuration the impact of
any these types of failures will be dependent upon what type of failure is
experienced, and how concurrent processing is distributed among the nodes in
the configuration. Parallel Concurrent Processing provides seamless failover
for a Concurrent Processing environment in the event that any of these types of
failures takes place.
In an Applications environment where the database tier utilizes Listener (
server) load balancing is implemented, and in a non-load balanced environment,
there are changes that must be made to the default configuration generated by
Autoconfig so that CP initialization, processing, and PCP functionality are
initiated properly on their respective/assigned nodes. These changes are
described in the next section - Concurrent Manager Setup and Configuration
Requirements in an 11i RAC Environment.
The current Concurrent Processing architecture with Global Service Management
consists of the following processes and communication model, where each process
is responsible for performing a specific set of routines and communicating with
parent and dependent processes.
아래 내용은 PCP환경에서 ICM, FNDSM, IM, Standard Manager의 역활을 설명하고
있습니다.
Internal Concurrent Manager (FNDLIBR process) - Communicates with the Service
Manager.
The Internal Concurrent Manager (ICM) starts, sets the number of active
processes, monitors, and terminates all other concurrent processes through
requests made to the Service Manager, including restarting any failed processes.
The ICM also starts and stops, and restarts the Service Manager for each node.
The ICM will perform process migration during an instance or node failure.
The ICM will be
active on a single node. This is also true in a PCP environment, where the ICM
will be active on at least one node at all times.
Service Manager (FNDSM process) - Communicates with the Internal Concurrent
Manager, Concurrent Manager, and non-Manager Service processes.
The Service Manager (SM) spawns, and terminates manager and service processes (
these could be Forms, or Apache Listeners, Metrics or Reports Server, and any
other process controlled through Generic Service Management). When the ICM
terminates the SM that
resides on the same node with the ICM will also terminate. The SM is ？hained?
to the ICM. The SM will only reinitialize after termination when there is a
function it needs to perform (start, or stop a process), so there may be
periods of time when the SM is not active, and this would be normal. All
processes initialized by the SM
inherit the same environment as the SM. The SM environment is set by APPSORA.
env file, and the gsmstart.sh script. The TWO_TASK used by the SM to connect
to a RAC instance must match the instance_name from GV$INSTANCE. The apps_<sid>
listener must be active on each CP node to support the SM connection to the
local instance. There
should be a Service Manager active on each node where a Concurrent or non-
Manager service process will reside.
Internal Monitor (FNDIMON process) - Communicates with the Internal Concurrent
Manager.
The Internal Monitor (IM) monitors the Internal Concurrent Manager, and
restarts any failed ICM on the local node. During a node failure in a PCP
environment the IM will restart the ICM on a surviving node (multiple ICM's may
be started on multiple nodes, but only the first ICM started will eventually
remain active, all others will gracefully terminate). There should be an
Internal Monitor defined on each node
where the ICM may migrate.
Standard Manager (FNDLIBR process) - Communicates with the Service Manager and
any client application process.
The Standard Manager is a worker process, that initiates, and executes client
requests on behalf of Applications batch, and OLTP clients.
Transaction Manager - Communicates with the Service Manager, and any user
process initiated on behalf of a Forms, or Standard Manager request. See Note:
240818.1 regarding Transaction Manager communication and setup requirements for
RAC.
Concurrent Manager Setup and Configuration Requirements in an 11i RAC
Environment
PCP를 사용하기위한 기본적인 Setup 절차를 설명하고 있습니다.
In order to set up Setup Parallel Concurrent Processing Using AutoConfig with
GSM,
follow the instructions in the 11.5.8 Oracle Applications System Administrators
Guide
under Implementing Parallel Concurrent Processing using the following steps:
1. Applications 11.5.8 and higher is configured to use GSM. Verify the
configuration on each node (see WebIV Note:165041.1).
2. On each cluster node edit the Applications Context file (<SID>.xml), that
resides in APPL_TOP/admin, to set the variable <APPLDCP oa_var="s_appldcp">
ON </APPLDCP>. It is normally set to OFF. This change should be performed
using the Context Editor.
3. Prior to regenerating the configuration, copy the existing tnsnames.ora,
listener.ora and sqlnet.ora files, where they exist, under the 8.0.6 and iAS
ORACLE_HOME locations on the each node to preserve the files (i.e./<some_
directory>/<SID>ora/$ORACLE_HOME/network/admin/<SID>/tnsnames.ora). If any of
the Applications startup scripts that reside in COMMON_TOP/admin/scripts/<SID>
have been modified also copy these to preserve the files.
4. Regenerate the configuration by running adautocfg.sh on each cluster node as
outlined in Note:165195.1.
5. After regenerating the configuration merge any changes back into the
tnsnames.ora, listener.ora and sqlnet.ora files in the network directories,
and the startup scripts in the COMMON_TOP/admin/scripts/<SID> directory.
Each nodes tnsnames.ora file must contain the aliases that exist on all
other nodes in the cluster. When merging tnsnames.ora files ensure that each
node contains all other nodes tnsnames.ora entries. This includes tns
entries for any Applications tier nodes where a concurrent request could be
initiated, or request output to be viewed.
6. In the tnsnames.ora file of each Concurrent Processing node ensure that
there is an alias that matches the instance name from GV$INSTANCE of each
Oracle instance on each RAC node in the cluster. This is required in order
for the SM to establish connectivity to the local node during startup. The
entry for the local node will be the entry that is used for the TWO_TASK in
APPSORA.env (also in the APPS<SID>_<HOSTNAME>.env file referenced in the
Applications Listener [APPS_<SID>] listener.ora file entry "envs='MYAPPSORA=<
some directory>/APPS<SID>_<HOSTNAME>.env)
on each node in the cluster (this is modified in step 12).
7. Verify that the FNDSM_<SID> entry has been added to the listener.ora file
under the 8.0.6 ORACLE_HOME/network/admin/<SID> directory. See WebiV Note:
165041.1 for instructions regarding configuring this entry. NOTE: With the
implementation of GSM the 8.0.6 Applications, and 9.2.0 Database listeners
must be active on all PCP nodes in the cluster during normal operations.
8. AutoConfig will update the database profiles and reset them for the node
from which it was last run. If necessary reset the database profiles back to
their original settings.
9. Ensure that the Applications Listener is active on each node in the cluster
where Concurrent, or Service processes will execute. On each node start the
database and Forms Server processes as required by the configuration that
has been implemented.
10. Navigate to Install > Nodes and ensure that each node is registered. Use
the node name as it appears when executing a nodename?from the Unix prompt on
the server. GSM will add the appropriate services for each node at startup.
11. Navigate to Concurrent > Manager > Define, and set up the primary and
secondary node names for all the concurrent managers according to the
desired configuration for each node workload. The Internal Concurrent
Manager should be defined on the primary PCP node only. When defining the
Internal Monitor for the secondary (target) node(s), make the primary node (
local node) assignment, and assign a secondary node designation to the
Internal Monitor, also assign a standard work shift with one process.
12. Prior to starting the Manager processes it is necessary to edit the APPSORA.
env file on each node in order to specify a TWO_TASK entry that contains
the INSTANCE_NAME parameter for the local nodes Oracle instance, in order
to bind each Manager to the local instance. This should be done regardless
of whether Listener load balancing is configured, as it will ensure the
configuration conforms to the required standards of having the TWO_TASK set
to the instance name of each node as specified in GV$INSTANCE. Start the
Concurrent Processes on their primary node(s). This is the environment
that the Service Manager passes on to each process that it initializes on
behalf of the Internal Concurrent Manager. Also make the same update to
the file referenced by the Applications Listener APPS_<SID> in the
listener.ora entry "envs='MYAPPSORA= <some directory>/APPS<SID>_<HOSTNAME>.
env" on each node.
13. Navigate to Concurrent > Manager > Administer and verify that the Service
Manager and Internal Monitor are activated on the secondary node, and any
other addititional nodes in the cluster. The Internal Monitor should not be
active on the primary cluster node.
14. Stop and restart the Concurrent Manager processes on their primary node(s),
and verify that the managers are starting on their appropriate nodes. On
the target (secondary) node in addition to any defined managers you will
see an FNDSM process (the Service Manager), along with the FNDIMON process (
Internal Monitor).
Reference Documents
Note 241370.1

What is your database version? OS?
We are using VCP suite for Planning Purpose. We are using VCP environment (12.1.3) in Decentralized structure connecting to 3 differect source environment ( consisting 11i and R12). As per the Oracle Note {RAC Configuration Setup For Running MRP Planning, APS Planning, and Data Collection Processes [ID 279156]} we have implemented RAC in our test environment to get better performance.
But after doing all the setups and concurrent programs assignment to different nodes, we are seeing huge performance issue. The Complete Collection which takes generally on an avg 180 mins in Production, is taking more than 6 hours to complete in RAC.
So I would like to get suggestion from this forum, if anyone has implemented RAC in pure VCP (decentralized) environment ? Will there be any improvement if we make our VCP Instance in RAC ?Do you PCP enabled? Can you reproduce the issue when you stop the CM?
Have you reviewed these docs?
Value Chain Planning - VCP - Implementation Notes & White Papers [ID 280052.1]
Concurrent Processing - How To Ensure Load Balancing Of Concurrent Manager Processes In PCP-RAC Configuration [ID 762024.1]
How to Setup and Run Data Collections [ID 145419.1]
12.x - Latest Patches and Installation Requirements for Value Chain Planning (aka APS Advanced Planning & Scheduling) [ID 746824.1]
APSCHECK.sql Provides Information Needed for Diagnosing VCP and GOP Applications Issues [ID 246150.1]
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

Number of concurrent managers

Hi,
how to change the number of concurrent managers ?
Many thanks before.

Hi Shashi,
In our R12 test environments , the defualt number of concurrent managers are 3, where as the average number of Concurrent Request are 12 at a time and see 20-30 concurrent requests in pending and nothing in CRM. Can you please advise how can I increase the default number of concurrent manager from 3 to 8. Do you mean number of CM or number of processes? If you want to increase the number of concurrent managers, refer to the document below. For increasing the number of processes you can do from (Concurrent > Manager > Define).
Also we has custom requests with an average of 1-2 at a time, so reading on some of the previous posts, It was recommended to have custom manager to handle the custom request. Can you please tell me how to create Custom Managers.It is recommended you have custom concurrent managers to process your custom concurrent programs.
Note: 170524.1 - How to Create a Custom Concurrent Manager
Oracle Applications System Administrator's Guide Documentation Set
http://www.oracle.com/technology/documentation/applications.html
Thanks,
Hussein

Acutal and Target Processes for two concurrent managers refuse to be equal

Hi
I have bounced the concurrent manager. I have stopped all services on the apps node then started them again.
All Actual / Target processes are now equal except two -
the OAM Generic Collection and the Output Post Processor
What, if anything, can I do for this? As they satnd, Concurrent Manger is down, still.
Thanks
EBS 11.5.10
AIX 5.2
Oracle 9.2.0.8

Someone here tells me that it isn't a good idea to worry about the iniquity of the Actual and Targer processes, if the particular manager is not one that we need, or use.
I dont know if this is correct or not.
He also tells me that checking the Dashboard to see if the CCM is up is not recommended - he explains that he only visits the Administer Concurrent Managers screen, and its there and only there that he compares the Actual to the Target.
I am not sure if he is right, but at least this question is now partly answered.
Also, I just read that "sometimes the actual process may be less than the target process due to manager deactivation" .
Thanks.
Edited by: Dan A on Dec 10, 2008 10:37 AM

Concurrent Managers & request monitoring and tunning

Hi,
Kindly share with me some scripts if you have for Concurrent Managers & request monitoring and tunning.
Many thanks before.

Check the following Metalink Notes:
Note: 169935.1 - Troubleshooting Oracle Apps Performance Issues
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=169935.1
Note: 108185.1 - Oracle Applications Object Library SQL scripts
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=108185.1
Note: 104664.1 - Setup & Usage (Concurrent Manager Unix specific)
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=104664.1
Note: 187504.1 - bde_request.sql - Process and Session info for one Concurrent Request (11.5)
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=187504.1
You may also use Oracle Application Manager (OAM) to monitor the concurrent managers and requests.

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

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

Concurrent managers down

Dear All,
Today morning concurrent managers were down on production. when i checked the concurrent logs observed the following error.
Shutting down Concurrent Manager : 27-FEB-2012 04:21:24
List of errors encountered:
_ 1 _
Routine AFPSMG encountered an ORACLE error. ORA-00604: error occurred
at recursive SQL level 2
ORA-04031: unable t.
Review your error messages for the cause of the error. (=<POINTER>)
_ 2 _
Routine AFPGSR encountered an ORACLE error. ORA-04031: unable to
allocate 16 bytes of shared memory ("shared pool".
Review your error messages for the cause of the error. (=<POINTER>)
then we restarted the cocurrent managers and they are working fine.
I just want to know the cause of this error.
Thanks.

Hi
The error :ORA-04031: unable to allocate 16 bytes of shared memory.
indicates that there is not enough sufficient memory in the shared pool for the processes
You need to check the alert log file of the database to see if there are similar error messages and then do Flush shared pool. This should take care of the issue if it has come once.
ALTER SYSTEM FLUSH SHARED_POOL;
If this does not work:
Increase the shared memory or a simple DB bounce could resolve the issue.
Regards
Shalini

Concurrent managers problem 11.5.9

I got through the process and reinstalled 11.5.9
but now I m getting a problem of starting my concurrent manager
I heard there is a patch for it but that requires me to raise a TAR which I don have access for.
Can u tell me a workaround on it

Hi,
I believe the scripts are helpful. However, you can query FND_CONCURRENT_QUEUES tables for details about the CM (refer to eTRM for details about the table/columns).
eTRM
http://etrm.oracle.com
To receive alerts, you can make use if the scripts (or the table), check the status of Concurrent Managers, and integrate this with Oracle Alert.
11i (11.5.10.2+ virtual) Documentation Library
http://download-uk.oracle.com/docs/cd/B25516_14/current/html/docset.html
You may also monitor the CM from the OS (write a shell script to monitor FNDLIB processes, and make it sends an email in case the number of processes is less than the actual running processes (or zero)).
Sorry, I do not have any script to share as I am using those scripts in the note referenced above.
Regards,
Hussein

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.

List of Concurrent managers and services

I am trying to find a listing of all the concurrent managers and services and what they do but I can't find this info all in one place, does anybody have an idea where i can find this?

Hi,
Refer to "Oracle Applications System Administrator's Documentation Set".
11i (11.5.10.2+ virtual) Documentation Library
http://download-uk.oracle.com/docs/cd/B25516_14/current/html/docset.html
Release 12.0.4 Documentation Library
http://download.oracle.com/docs/cd/B40089_09/current/html/docset.html
You can also query FND_CONCURRENT_QUEUES table which stores information about concurrent managers. Each row includes the name and description of a concurrent manager, as well as values that identify the program library attached to the manager.
Regards,
Hussein

What is the function of the Service Manager, in Concurrent Managers?

Greetings to All,
When looking at the concurrent managers, our internal manager is down and we also have the Service Manager being down. I understand the process of the Internal Manager.
But like to know what the Service Manager does and what it is used for.
Thanks in advance for any helpful information.

Hi,
Please refer to the following documents.
Note: 210062.1 - Generic Service Management (GSM) in Oracle Applications 11i
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=210062.1
Oracle® Applications System Administrator’s Guide Maintenance/Configuration manuals
http://www.oracle.com/technology/documentation/applications.html
Regards,
Hussein

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

Oracle concurrent managers setup recommendations

Similar Messages

Maybe you are looking for