CPU를 많이 점유하는 CONCURRENT MANAGER PROCESSES 의 조치방법

제품 : AOL
작성날짜 : 2004-11-30
CPU를 많이 점유하는 CONCURRENT MANAGER PROCESSES 의 조치방법
================================================
PURPOSE
OS상에서 TOP/TOPAS같은 Monitoring tool로 볼때 FNDLIBR process중 과도하게 CPU를 많이 차지하는 것을 확인할때가 있다. 이는 CM Setup의 조정을 통해
일부 해소할수 있다. 이 Note는 이에 대해 기술하고 있다.
Explanation
우선 Process의 갯수, Sleep time을 확인해야 한다.
Process한개당 CPU 점유율을 줄이기 위해서는 Process의 갯수를 줄이고 Sleep time을 늘려줘야 한다.
1. Select the System Administrator Responsibility
2. (N)Concurrent -> Manager -> Define
3. Look up the manager that is taking all the CPU.
4. Click on the Work Shifts button. Here, you can find the number or target
processes and the sleep time.
5. Lower the number of processes, or increase the sleep time.
6. Restart the manager for the changes to take effect.
Example
만약 manager 한개당 10개의 process , Sleep time 3을 지정했다면, 10개의 process가 3초에 한번씩 처리할 job 이 있는지 확인하고 이런 빈번한 확인이 시스템에 부하를 줄수 있으므로 Sleep time을 늘리고 이를 확인하는 process의 갯수를 줄여줘야 한다.
Reference Documents
<Note:114380.1>

Similar Messages

How to determine optimal no of concurrent manager processes

Hi,
We have a PROD env with 8 cpu and 64 G in database tier which is also the conc processing tier. The release version is 12.0.4 and OS is HP Itanium. Currently there are more than 160 conc manager processes running including the standard manager and is creating huge load during peak hrs. I want to cut down on the number of processes and implement the optimal no of processes. Looking for some suggestion on the same.
Is there any algorithm to calculate the optimal no of processes that should run depending on system hardware resource, no of users etc..
Thanks
Rit

Hi,
I do not believe such a formula exists or documented somewhere. I believe you need to tune you concurrent managers, and this depends on many factors (number of CPUs, number of users, number of concurrent requests, ..etc).
I would suggest you go through the following documents for some recommendations. You will have to adjust the Concurrent Managers parameters according to the load you have until you are satisfied with the performance. Make sure you consider reviewing the following parameters/factors:
- PMON cycle
- Sleep time
- Cache size
- Number of records in CM tables (using "Purge Concurrent Requests And/Or Manager Data" concurrent program)
- Number of standard managers
- Statistics for CM tables (using "Gather Table Statistics" concurrent program)
Note: 105133.1 - Concurrent Manager Questions and Answers Relating to Generic Platform
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=105133.1
Note: 211362.1 - Process Monitor Session Cycle Repeats Too Frequently
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=211362.1
Note: 117648.1 - Troubleshooting Performance Issues in Oracle Applications/ E-Business Suite
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=117648.1
Note: 114380.1 - Concurrent Manager Processes Taking Lots of CPU
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=114380.1
Note: 178925.1 - How to change the sleep time for a Concurrent Manager
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=178925.1
Note: 155170.1 - How to Change the Sleep Time Parameter Setting for Internal Concurrent Manager
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=155170.1
Note: 270458.1 - How to Reduce the Wait Time Between Spawned Concurrent Requests
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=270458.1
Note: 182154.1 - Summary of Possible Reasons and Solutions for the Problem Where All Concurrent Requests Stuck in Pending Phase
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=182154.1
Regards,
Hussein

Kill Concurrent manager process

Hi experts,
we deactivate the concurrent process by using concurrent process id,it showing the status "Deactivating"
we would like to be status should be "Deactivated".
what i should do that?
Thanks
sundar.

Sundar,
Run cmclean.sql and check then.
Note: 134007.1 - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=134007.1

Concurrent Manager Processes Load Balancing....

Hi,
Could a concurrent managers process be spread across multiple application nodes in a PCP and RAC environment...?

Hi;
Please check below thread&notes and see its helpful for your issue:
Advanced Configurations and Topologies for Enterprise Deployments of E-Business Suite 11i [ID 217368.1] ( part: Option 2.5. Concurrent Layer Load Balancing )
Also see:
Re: Configuring Parallel Concurrent Processing with ssh
Load Balancing for EBS R12
Steps to setup load balancing
Re: Load Balancing for EBS R12
Regard
Helios

Concurrent Manager - Actual processes

Oracle EBS 11.5.9 on Windows 2003
1-In administer concurrent Managers screen.
against STANDARD MANAGER, i am not able to see ACTUAL process where as in TARGET & RUNNING columns are showing values.
I think it happend after cloning, on production i am able see ACTUAL processes.
2-The problem is basically, concurrent manager processing is very slow.
How i can troubleshoot above two points.
Regards,

Hi,
1-In administer concurrent Managers screen.
against STANDARD MANAGER, i am not able to see ACTUAL process where as in TARGET & RUNNING columns are showing values.
I think it happend after cloning, on production i am able see ACTUAL processes. Any errors in the CM log file?
From System Administrator responsibility, navigate to Concurrent > Manager > Administer. Query "Standard Manager", click on "Work Shifts" and verify the number of Processes.
2-The problem is basically, concurrent manager processing is very slow.Do you run "Purge Concurrent Request and/or Manager Data" concurrent program on regular basis?
How many rows you have in the FND_CONCURRENT_PROCESSES and FND_CONCURRENT_REQUESTS tables? Make sure it does in exceed 50K by running "Purge Concurrent Request and/or Manager Data" concurrent program.
Regards,
Hussein

Concurrent Manager Issue in Oracle Apps 11i on MS Windows 2003

Hi,
We have Oracle Apps 11i (11.5.10) on Windows 2003 running Oracle Financilas and Supply Chain.
From this morning onwards, concurrent requests are not getting completed. All requests are showing Running Normally. I checked the server (Single Node 4 GB Memory) and CPU usage is more than 90%. Task Manager is showing 50% CPU usage for SYSTEM (Image Name). Once the CPU usage for SYSTEM(image name) goes beyond 40% then the server is becoming slow and the problem starts.
When I stop the Concurrent Manager it does not stop and I have to End Process the FNDLIBR process manually.
I have recreated the concurrent manager using CCMSETUP and also ran cmclean.sql. Nothing is helping.
System is Live since 2006 and the issue started only today.
Please suggest any solutions as this is happening in our Production system.
Thanks.
Thiru

Thiru,
Which concurrent manager consumes the CPU usage? Are you able to identify it?
Any errors in the CM log file? Did you try to start the CM with diag=y and see if any errors are reported in the log files?
What happen to the CPU usage when you stop the CM?
I assume that you are running Purge Concurrent Manager/Requests on regular basis, so this should not be an issue here.
Please review the following notes, and see if it helps.
Note: 114380.1 - Concurrent Manager Processes Taking Lots of CPU
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=114380.1
Note: 264752.1 - FNDLIBR Consuming Memory Causing CPU Utilization To Increase Daily
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=264752.1
System is Live since 2006 and the issue started only today.I assume no changes have been done recently, correct?
Regards,
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

Re: concurrent manager quest

Hello,
Sometimes even we kill the concurrent manager process at os level but that session still exits in the database.So now how can we verify the control code of concurrent managers in the database.Kindly tell me.
Thanks ,
928714.

Sometimes even we kill the concurrent manager process at os level but that session still exits in the database.So now how can we verify the control code of concurrent managers in the database.Kindly tell me.If you kill the CM process from the OS, you do not need to kill any concurrent manager sessions from the database.
If you terminate a concurrent request, then you can kill the database sessions (if any exist) from the database using (Concurrent Processing - How to Find Database Session & Process Associated with a Concurrent Program Which is Currently Running. [ID 735119.1]).
Thanks,
Hussein

Concurrent Manager start/stop EBS R12

Hi all,
I am starting all the processes/services in my EBS R12 as APPLMGR user,
using the shell script:
$ adstrtal.sh apps/apps
and to stop it with:
$ adstpall.sh apps/apps
But when I run the stop script, I still see the Concurrent Manager process active
(ps -ef|grep FNDLIBR).
Does adstpall.sh do not contain the script to stop CM?
Thanks a lot

I just get paranoid when it keeps emailing the APPLMGR user that the CM died -giving up What is the message you get? If it says "successfully" then you can ignore the message.

Routine AFPEIM encountered an error while starting concurrent manager STAND

hi,
Today i have done cloning and clone completed successfully. but CM is not comming up. I found the following errors in the concurrent log. Any hints on this.
==========================================
Starting INVTMRPM Concurrent Manager : 28-FEB-2012 13:33:48
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager INVTMRPM with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INCTM.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:48
Starting INVTMRPM Concurrent Manager : 28-FEB-2012 13:33:48
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager INVTMRPM with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INCTM.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:48
Starting INVTMRPM Concurrent Manager : 28-FEB-2012 13:33:48
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager INVTMRPM with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INCTM.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:48
Starting INVTMRPM Concurrent Manager : 28-FEB-2012 13:33:48
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager INVTMRPM with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INCTM.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:48
Starting INVTMRPM Concurrent Manager : 28-FEB-2012 13:33:48
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager INVTMRPM with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INCTM.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:48
Starting PODAMGR Concurrent Manager : 28-FEB-2012 13:33:48
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library /eqaappl/drqaebiz/appl/po/11.5.0/bin/POXCON.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator t : 28-FEB-2012 13:33:49
Starting PODAMGR Concurrent Manager : 28-FEB-2012 13:33:49
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library /eqaappl/drqaebiz/appl/po/11.5.0/bin/POXCON.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator t : 28-FEB-2012 13:33:49
Starting PODAMGR Concurrent Manager : 28-FEB-2012 13:33:49
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager PODAMGR with library /eqaappl/drqaebiz/appl/po/11.5.0/bin/POXCON.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator t : 28-FEB-2012 13:33:49
Starting RCVOLTM Concurrent Manager : 28-FEB-2012 13:33:49
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager RCVOLTM with library /eqaappl/drqaebiz/appl/po/11.5.0/bin/RCVOLTM.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
Starting RCVOLTM Concurrent Manager : 28-FEB-2012 13:33:49
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager RCVOLTM with library /eqaappl/drqaebiz/appl/po/11.5.0/bin/RCVOLTM.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
Starting RCVOLTM Concurrent Manager : 28-FEB-2012 13:33:49
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager RCVOLTM with library /eqaappl/drqaebiz/appl/po/11.5.0/bin/RCVOLTM.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
Starting INVMGR Concurrent Manager : 28-FEB-2012 13:33:49
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager INVMGR with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INVLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
Starting INVMGR Concurrent Manager : 28-FEB-2012 13:33:49
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager INVMGR with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INVLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
Starting INVMGR Concurrent Manager : 28-FEB-2012 13:33:49
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager INVMGR with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INVLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
Starting INVMGR Concurrent Manager : 28-FEB-2012 13:33:49
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager INVMGR with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INVLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:49
Starting INVMGR Concurrent Manager : 28-FEB-2012 13:33:49
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager INVMGR with library /eqaappl/drqaebiz/appl/inv/11.5.0/bin/INVLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:50
Starting TDSMGR Concurrent Manager : 28-FEB-2012 13:33:50
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager TDSMGR with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:50
Starting TDSMGR Concurrent Manager : 28-FEB-2012 13:33:50
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager TDSMGR with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:50
Starting TDSMGR Concurrent Manager : 28-FEB-2012 13:33:50
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager TDSMGR with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator : 28-FEB-2012 13:33:50
Starting XDP_MANAGER Concurrent Manager : 28-FEB-2012 13:33:50
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager XDP_MANAGER with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administr : 28-FEB-2012 13:33:50
Starting XDP_MANAGER Concurrent Manager : 28-FEB-2012 13:33:50
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager XDP_MANAGER with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administr : 28-FEB-2012 13:33:50
Starting XDP_MANAGER Concurrent Manager : 28-FEB-2012 13:33:50
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager XDP_MANAGER with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administr : 28-FEB-2012 13:33:50
Starting XDP_MANAGER Concurrent Manager : 28-FEB-2012 13:33:50
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager XDP_MANAGER with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administr : 28-FEB-2012 13:33:50
Starting XDP_MANAGER Concurrent Manager : 28-FEB-2012 13:33:50
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager XDP_MANAGER with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administr : 28-FEB-2012 13:33:50
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:50
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:50
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:50
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:51
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:51
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:52
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:52
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:53
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:53
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:53
Starting STANDARD Concurrent Manager : 28-FEB-2012 13:33:53
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /eqaappl/drqaebiz/appl/fnd/11.5.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrato : 28-FEB-2012 13:33:53
Starting PASMGR Concurrent Manager : 28-FEB-2012 13:33:53
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager PASMGR with library /eqaappl/drqaebiz/appl/pa/11.5.0/bin/PALIBR.
Check that your system has enough resources to start a concurrent manager process. Contact your system administrator to : 28-FEB-2012 13:33:53
Process monitor session ended : 28-FEB-2012 13:33:53
==========================================
i have done already steps mentioned in 1312632.1 but nor worked for me.
also i ran below command and output is as follows.
SQL> select CONCURRENT_QUEUE_NAME
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME like 'FNDSM%';
2 3
CONCURRENT_QUEUE_NAME
FNDSM_DRQAEBS
SQL>
Version details are 11.5.10.2 and DB is 11g.
Regards
DBA.

Hi;
Please see:
R12 instance Concurrent manager and host status is showin as down
Regard
Helios

CONCURRENT MANAGER STARTUP 시의 일반적인 문제 및 해결 방법

제품 : AOL
작성날짜 : 2003-12-02
CONCURRENT MANAGER STARTUP 시의 일반적인 문제 및 해결 방법
=============================================
PURPOSE
Concurrent Manager Startup 시에 발생할수 있는 일반적인 문제및 해결법.
Explanation
Concurrent Process 의 비정상적인 종료로 인하여, Concurrent Manager 의 Startup 이 정상적으로 되지 않는 경우의 해결방법.
Example
1. Concurrent Manager Log file의 Check.
2. FNDLIBR, FNDCRM 및 실행중인 Concurrent Manager Process 가 없는지
확인.
3. Update the fnd_concurrent_requests table
set phase_code = 'C', status_code = 'X'
where status_code = 'T';
4. Update fnd_concurrent_queues set running_processes = 0
5. Update fnd_concurrent_queues set max_processes = 0
6. Check the fnd_concurrent_proccesses table if there is a process with
process_status_code = A, change it to 'K'.
7. Check the system to see if any process has a lock on the table
FND_CONCURRENT_PROCESSES
8. Start the concurrent managers using the script adcmctl.sh
Reference Documents
1. <Note:149472.1> How to fix common Concurrent Manager Startup problems
2. <Note:134007.1> CMCLEAN.SQL - Non Destructive Script to Clean
Concurrent Manager Tables
3. <Note:104541.1> Troubleshooting (Concurrent Manager Generic)
4. <Note:69336.1> Basic information about Concurrent Managers
Step 5 & 6

Concurrent Manager doubt

Hello all,
We have 3 db node rac and 4 apps services.
concurrent mangegers are running in apps nodes. now I want to bring down db node1 and shutdown managers on node1.
here my question is if i want the mangers to run on other nodes so tht runnig jobs will not be impacted,wht is the process.
any chnages required in tns file.
pls suggest me the action plan.
Regards,
siva

Hi,
Please see these docs.
Concurrent managers not running/failing over to correct node in PCP/RAC environment [ID 790624.1]
How To Ensure Load Balancing Of Concurrent Manager Processes In PCP-RAC Configuration [ID 762024.1]
Parallel Concurrent Processing Failover/Failback Expectations [ID 271090.1]
Concurrent Manager Setup and Configuration Requirements in an 11i RAC Environment [ID 241370.1]
How to run a concurrent program against a specific RAC instance with PCP/RAC setup? [ID 1129203.1]
In A PCP/RAC Configuration, How To Find Out On Which RAC Instance FNDSM Is Currently Running? [ID 1089396.1]
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

Concurrent manager log CONC-SM TNS FAIL ICM failed to start for target MSOA

Hi all,
We are doing cloning from two node PCP with loadbalancer to single node application tier.
I did preclone in database and one of the node of application,
Run adcfgclone.pl in dbTier and AppsTier everything went smooth, But the Three managers are not coming up,
1. Internel manager
2.Standar manager
3.standard manager
Thease three managers are pointing to node" Prymary node of PCP
We followed the note: 555081.1 still the issue is same
The manager logfile shows:
"Check that your system has enough resources to start a concurrent manager process : 15-NOV-2008 21:20:22
Starting STANDARD Concurrent Manager : 15-NOV-2008 21:20:22
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /ebiz/u01/appltest/TEST/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /ebiz/u01/appltest/TEST/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process : 15-NOV-2008 21:20:23
Starting Internal Concurrent Manager Concurrent Manager : 15-NOV-2008 21:20:23
CONC-SM TNS FAIL
: ICM failed to start for target MSOAAPPL2. Review ICM log files for additional information.
Process monitor session ended : 15-NOV-2008 21:20:23"
Please help me out in resolving this
many thanks in advance..

Hi all,
Sorted out by changing the Primary node as thhe corect node and run cmclean.sql..
Now the managers are working file..
Thanks and Regards
Vasu

Programmatically cancelling a Concurrent Manager Job

We have a need to programmatically cancel a concurrent job that could be in a Pending or Running status.
We did some traces and did an update on the fnd_concurrent_requests table.
This sets the request status to Terminated. However, the job still sits in the Concurrent manager process "queue", and never gets totally cleaned.
Is there a way to programmatically, cleanly cancel a request?
Any insight would be helpful.
Thanks!

Hi,
Thanks for your response. We tried the status and phase code updates already. What we found that the row gets updated in fnd-conc-requests, but the request still remains in the queue in the session.
Another thing we are trying is to find the session and kill it using hte alter system command.This is expected if you have database sessions running the background and you will need to kill these sessions in addition to updating concurrent requests tables.
Note: 187504.1 - bde_request.sql - Process and Session info for one Concurrent Request (11.5)
Note: 735119.1 - How to Find Database Session & Process Associated with a Concurrent Program Which is Currently Running.
Regards,
Hussein

CPU를 많이 점유하는 CONCURRENT MANAGER PROCESSES 의 조치방법

Similar Messages

Maybe you are looking for