Concurrent manager restart

Hi all,
if the application is brought down while some concurrent programs are still in Queued status, will they start on their own after the application is brought back up, or will we need to rerun them?
Any suggestions..
Thanks in advance..

You do not have to resubmit those concurrent requests once the CM is up and running again, as it will process the requests already submitted.

Similar Messages

Concurrent manager status inactive every application services restart

ebs: 11.5.10.2
os: AIX 5
whenever im restarting application server i mean to take coldbackup or for any workaround
the concurrent manager are down i checked with command ps -ef|grep fndlibr|grep APPLMGR|wc -l it shows only one concuurent manager is running so i have to go for a Conccurent manager recover through OAM then all the conccurent manager are up the same ps -ef|grep fndlibr|grep APPLMGR|wc -l shows 15
while going through Conccurent manager recovery is gives me orphaned Process(which is a schedule request from user--iam unable to cancel the request it says the conccurent manager which was handling this request does not exist) which is supposed to be killed but im unable to kill it at oslevel
when i use kill -9 ospid it says ospid doesnt exist (may be it is ospid of the user system)
can anyone say me why is this happening and lead me to a solution?
shall i go for a cmclean and if yes then tell me what cm clean does...
Thanks
ApPsMasTI,
ShARinG Is CarInG

Hi;
You can run cmclean.sql. For details see:
CMCLEAN
Also see:
How To Clear Orphan Generate Run Balance Processes [ID 337898.1]
Regard
Helios

Concurrent manager not working on multi tier apps r12.1

Hi All,
I've created clone environment from our production environment, following details of the environment:
DB: 11.1.0.7 - 2 nodes RAC
APPS: 11.1.3 - 2 nodes
OS: LINUX 64bit
hosnames: terbdb1, terbdb2
my problem is any request immediately appear as inactive nomanager.
here's cm log file of both nodes:
TERBDB1:
========================================================================
Starting TEST_0620@TEST Internal Concurrent Manager -- shell process ID 22842
          logfile=/app1/TEST/inst/apps/TEST_terbdb1/logs/appl/conc/log/TEST_0620.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=30
             pmon=4
           quesiz=1
          Reviver is ENABLED
Routine &ROUTINE has attempted to start the internal concurrent manager. The ICM is already running. Contact you system administrator for further assistance.afpdlrq r
eceived 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.
Review concurrent manager log file for more detailed information. : 20-JUN-2013 00:57:38 -
Shutting down Internal Concurrent Manager : 20-JUN-2013 00:57:38
List of errors encountered:
_ 1 _
Routine AFPCSQ encountered an ORACLE error. .
Review your error messages for the cause of the error. (=<POINTER>)
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The TEST_0620@TEST internal concurrent manager has terminated with status 1 - giving up.
You have new mail in /var/spool/mail/applmgr
TERBDB2:
========================================================================
Starting TEST_0620@TEST Internal Concurrent Manager -- shell process ID 24424
          logfile=/app1/TEST/inst/apps/TEST_terbdb2/logs/appl/conc/log/TEST_0620.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=30
             pmon=4
           quesiz=1
          Reviver is ENABLED
+---------------------------------------------------------------------------+
Application Object Library: Concurrent Processing version 11.5
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
Internal Concurrent Manager started : 20-JUN-2013 00:53:21
+---------------------------------------------------------------------------+
                   Process monitor session started : 20-JUN-2013 00:53:21
Starting INVTMRPM Concurrent Manager               : 20-JUN-2013 00:53:21
Starting RCVOLTM Concurrent Manager                : 20-JUN-2013 00:53:21
Starting FFTM Concurrent Manager                   : 20-JUN-2013 00:53:21
Starting C_AQCT_SVC Concurrent Manager             : 20-JUN-2013 00:53:21
Starting FNDCPOPP Concurrent Manager               : 20-JUN-2013 00:53:21
Starting DownloadProcessorMigrationMode Concurrent Manager : 20-JUN-2013 00:53:22
Starting DownloadProcessorNormalMode Concurrent Manager : 20-JUN-2013 00:53:22
Starting FNDCRM Concurrent Manager                 : 20-JUN-2013 00:53:22
Starting FNDSCH Concurrent Manager                 : 20-JUN-2013 00:53:22
Starting AMSDMIN Concurrent Manager                : 20-JUN-2013 00:53:22
Starting OAMCOLMGR Concurrent Manager              : 20-JUN-2013 00:53:22
Starting IEU_WL_CS Concurrent Manager              : 20-JUN-2013 00:53:22
Starting PASMGR Concurrent Manager                 : 20-JUN-2013 00:53:22
Starting IEU_SH_CS Concurrent Manager              : 20-JUN-2013 00:53:22
                     Process monitor session ended : 20-JUN-2013 00:53:22
Kindly advice.
Regards,
Ahmed

Salam Hussein,
this's output of PROD:
SQL> select concurrent_queue_name, p.node_name, db_instance
2 from fnd_concurrent_processes p, fnd_concurrent_queues q, fnd_cp_services s
3 where p.queue_application_id = q.application_id
4 and p.concurrent_queue_id = q.concurrent_queue_id
5 and q.manager_type = s.service_id
6 and p.process_status_code = 'A';
CONCURRENT_QUEUE_NAME          NODE_NAME                      DB_INSTANCE
FNDCRM                         ERPAPP1                        MCITERP1
FNDICM                         ERPAPP1                        MCITERP1
FNDSCH                         ERPAPP1                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
CONCURRENT_QUEUE_NAME          NODE_NAME                      DB_INSTANCE
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
STANDARD                       ERPAPP2                        MCITERP1
PODAMGR                        ERPAPP1                        MCITERP1
PODAMGR                        ERPAPP1                        MCITERP1
PODAMGR                        ERPAPP1                        MCITERP1
PODAMGR                        ERPAPP1                        MCITERP1
CONCURRENT_QUEUE_NAME          NODE_NAME                      DB_INSTANCE
RCVOLTM                        ERPAPP1                        MCITERP1
PASMGR                         ERPAPP2                        MCITERP1
INVMGR                         ERPAPP2                        MCITERP1
INVTMRPM                       ERPAPP1                        MCITERP1
WFALSNRSVC                     ERPAPP1                        MCITERP2
WFMLRSVC                       ERPAPP1                        MCITERP1
FTE_TXN_MANAGER                ERPAPP2                        MCITERP1
IEU_SH_CS                      ERPAPP1                        MCITERP1
IEU_WL_CS                      ERPAPP1                        MCITERP1
OAMCOLMGR                      ERPAPP1                        MCITERP1
FNDSM_ERPAPP2                  ERPAPP2                        MCITERP1
CONCURRENT_QUEUE_NAME          NODE_NAME                      DB_INSTANCE
FNDSM_ERPAPP1                  ERPAPP1                        MCITERP1
WFWSSVC                        ERPAPP1                        MCITERP2
AMSDMIN                        ERPAPP1                        MCITERP1
FNDCPOPP                       ERPAPP2                        MCITERP2
FFTM                           ERPAPP1                        MCITERP1
38 rows selected.
Regards,
Ahmed

Internal concurrent manager is not up

HI
db : 11g
apps : 11.5.10.2
I found this error in internal conc mgr log file.
APP-FND-01564: ORACLE error 1 in insert_icm_record
Cause: insert_icm_record failed due to ORA-00001: unique constraint (APPLSYS.FND_CONCURRENT_PROCESSES_U1) violated.
The SQL statement being executed at the time of the error was: INSERT INTO FND_CONCURRENT_PROCESSES (CONCURRENT_PROCESS_ID, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, ORACLE_PROCESS_ID, QUEUE_APPLICATION_ID, CONCURRENT_QUEUE_ID, OS_PROCESS_ID, SESSION_ID, PROCESS_START_DATE, PROCESS_STATUS_CODE, MANAGER_TYPE, NODE_NAME, DB_NAME, DB_DOMAIN, SQLNET_STRING, DB_INSTANCE, Instance_Number) VALUES (:cpid, SYSDATE, SYSDATE, :mgrusrid, :mgrusrid, :opid, :qappid, :qid, :ospid, :osid, SYSDATE, 'A', 0, :node, :dbname, :dbdomain, :dbinst, (Select instance_name from v$instance), (Select instance_number from v$instance)) and was executed from the file &ERRFILE.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The PROJ2_0907@PROJ2 internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting PROJ2_0907@PROJ2 Internal Concurrent Manager -- shell process ID 7041
logfile=/oracle/instance/proj2/proj2comn/admin/log/PROJ2_rh53vm01/PROJ2_0907.mgr
PRINTER=noprint
mailto=oracle
restart=N
diag=N
sleep=60 (default)
pmon=20 (default)
quesiz=1 (default)
establish_icm - Unable to insert ICM record
Call to establish_icm failed
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 07-SEP-2009 06:36:25 -
Shutting down Internal Concurrent Manager : 07-SEP-2009 06:36:25
List of errors encountered:
_ 1 _
Routine AFPCSQ encountered an ORACLE error. .
Review your error messages for the cause of the error. (=<POINTER>)
APP-FND-01564: ORACLE error 1 in insert_icm_record
Cause: insert_icm_record failed due to ORA-00001: unique constraint (APPLSYS.FND_CONCURRENT_PROCESSES_U1) violated.
The SQL statement being executed at the time of the error was: INSERT INTO FND_CONCURRENT_PROCESSES (CONCURRENT_PROCESS_ID, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, ORACLE_PROCESS_ID, QUEUE_APPLICATION_ID, CONCURRENT_QUEUE_ID, OS_PROCESS_ID, SESSION_ID, PROCESS_START_DATE, PROCESS_STATUS_CODE, MANAGER_TYPE, NODE_NAME, DB_NAME, DB_DOMAIN, SQLNET_STRING, DB_INSTANCE, Instance_Number) VALUES (:cpid, SYSDATE, SYSDATE, :mgrusrid, :mgrusrid, :opid, :qappid, :qid, :ospid, :osid, SYSDATE, 'A', 0, :node, :dbname, :dbdomain, :dbinst, (Select instance_name from v$instance), (Select instance_number from v$instance)) and was executed from the file &ERRFILE.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The PROJ2_0907@PROJ2 internal concurrent manager has terminated with status 1 - giving up.
=============
_ 1 _
Routine AFPEIM encountered an ORACLE error. ORA-00001: unique
constraint (APPLSYS.FND_CONCURRENT_PROCESSES_U1) vio.
Review your error messages for the cause of the error. (=<POINTER>)
Where as all other conc mgr are up and when i submit one conc request it completed normal.
How should i bring the ICM up?
Thanks a lot................

Hi,
Please refer to (Note: 552142.1 - Error APP-FND-01564 ORA-00001 when Starting the Concurrent Managers).
Regards,
Hussein

Request set not getting picked up by concurrent manager.

Hi All
We have an issue today where the daily scheduled request set did not run and status for which remained at "Pending Scheduled". Concurrent Manager did not pick up this and status remained:
This request is waiting to be processed by the Conflict Resolution Manager.
This request cannot yet begin execution because other requests may conflict with it. The Conflict Resolution Manager will determine when this request may begin execution.
User <user_ name> submitted this request on 06-MAR-2011 23:17:33.
No action required. This is a normal condition.
This request may have to wait on one or more of the following requests to complete before it can begin execution:
I checked all the 'incompatibilities" of the programs for request set and none of them were running.
We did the below, but no success:
1. Restarted the concurret manager
2. Cancelled the scheduled run and submitted request set again.
Still the status remained at "Pending Scheduled" with above message.
When we tried to run the individaul programs for that request set it all worked fine. So I would like to know what could be the issue and how to overcome this. I think the issue could be with request set as the individual program is working fine.
Any pointers will be highly appriciated.
Many Thanks,
-Shashank

which manager is Processing that request.. if it is Custom manager Then U should excllude this concurrent program from the concurrent manager.
otherwise both the Standard manager or custom manager both are not going to pickup the process..
he
Please Check The Cocnurrent Manager which is going to process and check wether its included in the respective manager.
Thanks
Reddy
http://11iapps.wordpress.com

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

Oracle Fulfillment server does not start and also my concurrent manager is

The oracle Fulfillment server does not start and also my concurrent manager is down, when ever iam trying to start them i getting error.
even i restarted my laptop many times
Iam using WINXP on my laptop.
Pls help someone
hsawwan
Posts: 11,859
Registered: 03/13/06
Re: oracle Fulfillment server and concurrent manager problem
Posted: Oct 13, 2008 9:26 AM in response to: user578071 Reply
What is the error?
What does CM log file say?
Please run cmclean.sql and try to start the CM then.
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
where should i run in apps schema or some other schema, where can i find the log
as iam using r12

Duplicate thread ..
oracle Fulfillment server and concurrent manager problem
Re: oracle Fulfillment server and concurrent manager problem

Could not activate Internal Concurrent Manager

Hi all,
I downloaded ebiz suite from edelivery and installed it on my stand alone xp system, giving a random domain name during installation (and editing the etc/hosts file before that). For some reason I couldn't activate ICM in windows services folder listed as OracleConcMgr_VISLocalhost. I manually tried to start the service by clicking on start, it starts up and stays there for 10 secs and then shuts it self down. I even tried starting the ICM by running 'adcmctl start apps/apps'. But it simply exits with a status 0, and it doesn't generate any log file in viscomn/admin/logs/vis_localhost.
The output for the above command:
Starting concurrent manager for....
adcmctl.cmd exiting with status 0
I've also tried cmclean.sql. Please help me in solving this issue as all my request are in 'no manager available' status. I even tried re installing the apps but it still gives me the same error.
Thanks
Suneel

Fadi Hasweh, you rock!!!
It works!!!
Wierdly the tnsnames.ora file is located under F:\visora\8.0.6\NET80\ADMIN\VIS_localhost directory . I added the entries as you suggested and restarted the system. And that earlier error doesn't show up any more.
Now I got a new error when I try to run a report:
+---------------------------------------------------------------------------+
Receivables: Version : 11.5.0 - Development
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
ARXCTA module: Adjustment Approval Report
Current system time is 27-FEB-2007 11:06:31
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
P_ORDER_BY='Adjustment Name'
APPLLCSP Environment Variable set to :
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.UTF8
LOG :
Report: F:\visappl\ar\11.5.0\reports\US\ARXCTA.rdf
Logged onto server:
Username:
LOG :
Logged onto server:
Username: APPS
ERR REP-3002: Error initializing printer. Please make sure a printer is installed.
Program exited with status 3
Cause: The program terminated, returning status code 3.
Action: Check your installation manual for the meaning of this code on this operating system.
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 2719522.
Review your concurrent request log and/or report output file for more detailed information.
Executing request completion options...
Finished executing request completion options.
Concurrent request completed
Current system time is 27-FEB-2007 11:06:31
---------------------------------------------------------------------------

Internal Concurrent Manager is Not Active at this tim

Dear,
We are on 11.5.10,
Concurrent manager is not working properly. whenever, we start concurrent manager it's whow active but after few second approvx 15 second show not active.
Any boday have idea.
thanks

i have run cm clean and restart concurrement it was active but fiew second later it's showing inactive againg.
-- out put of log file.
========================================================================
Starting orcl_1211@orcl Internal Concurrent Manager -- shell process ID 5112060
          logfile=/apps/applmgr/orclcomn/admin/log/orcl_career1/orcl_1211.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=60 (default)
             pmon=20 (default)
           quesiz=1 (default)
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 11-DEC-2013 09:04:48 -
Shutting down Internal Concurrent Manager : 11-DEC-2013 09:04:48
List of errors encountered:
_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The orcl_1211@orcl internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting orcl_1211@orcl Internal Concurrent Manager -- shell process ID 4260082
          logfile=/apps/applmgr/orclcomn/admin/log/orcl_career1/orcl_1211.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=60 (default)
             pmon=20 (default)
           quesiz=1 (default)
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 11-DEC-2013 12:50:42 -
Shutting down Internal Concurrent Manager : 11-DEC-2013 12:50:42
List of errors encountered:
_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The orcl_1211@orcl internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting orcl_1211@orcl Internal Concurrent Manager -- shell process ID 15204490
          logfile=/apps/applmgr/orclcomn/admin/log/orcl_career1/orcl_1211.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=60 (default)
             pmon=20 (default)
           quesiz=1 (default)
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 11-DEC-2013 12:59:31 -
Shutting down Internal Concurrent Manager : 11-DEC-2013 12:59:31
List of errors encountered:
_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The orcl_1211@orcl internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting orcl_1211@orcl Internal Concurrent Manager -- shell process ID 20250840
          logfile=/apps/applmgr/orclcomn/admin/log/orcl_career1/orcl_1211.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=60 (default)
             pmon=20 (default)
           quesiz=1 (default)
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 11-DEC-2013 13:01:10 -
Shutting down Internal Concurrent Manager : 11-DEC-2013 13:01:10
List of errors encountered:
_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The orcl_1211@orcl internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting orcl_1211@orcl Internal Concurrent Manager -- shell process ID 4260094
          logfile=/apps/applmgr/orclcomn/admin/log/orcl_career1/orcl_1211.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=60 (default)
             pmon=20 (default)
           quesiz=1 (default)
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 11-DEC-2013 13:07:04 -
Shutting down Internal Concurrent Manager : 11-DEC-2013 13:07:04
List of errors encountered:
_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The orcl_1211@orcl internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting orcl_1211@orcl Internal Concurrent Manager -- shell process ID 19792126
          logfile=/apps/applmgr/orclcomn/admin/log/orcl_career1/orcl_1211.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=60 (default)
             pmon=20 (default)
           quesiz=1 (default)
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 11-DEC-2013 13:12:57 -
Shutting down Internal Concurrent Manager : 11-DEC-2013 13:12:57
List of errors encountered:
_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The orcl_1211@orcl internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting orcl_1211@orcl Internal Concurrent Manager -- shell process ID 11468854
          logfile=/apps/applmgr/orclcomn/admin/log/orcl_career1/orcl_1211.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=60 (default)
             pmon=20 (default)
           quesiz=1 (default)
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 11-DEC-2013 13:15:38 -
Shutting down Internal Concurrent Manager : 11-DEC-2013 13:15:38
List of errors encountered:
_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The orcl_1211@orcl internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting orcl_1211@orcl Internal Concurrent Manager -- shell process ID 21168284
          logfile=/apps/applmgr/orclcomn/admin/log/orcl_career1/orcl_1211.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=60 (default)
             pmon=20 (default)
           quesiz=1 (default)
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 11-DEC-2013 13:18:37 -
Shutting down Internal Concurrent Manager : 11-DEC-2013 13:18:37
List of errors encountered:
_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The orcl_1211@orcl internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting orcl_1211@orcl Internal Concurrent Manager -- shell process ID 16187636
          logfile=/apps/applmgr/orclcomn/admin/log/orcl_career1/orcl_1211.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=60 (default)
             pmon=20 (default)
           quesiz=1 (default)
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 11-DEC-2013 13:21:43 -
Shutting down Internal Concurrent Manager : 11-DEC-2013 13:21:43
List of errors encountered:
_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The orcl_1211@orcl internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting orcl_1211@orcl Internal Concurrent Manager -- shell process ID 15269970
          logfile=/apps/applmgr/orclcomn/admin/log/orcl_career1/orcl_1211.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=60 (default)
             pmon=20 (default)
           quesiz=1 (default)
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 11-DEC-2013 13:34:50 -
Shutting down Internal Concurrent Manager : 11-DEC-2013 13:34:50
List of errors encountered:
_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The orcl_1211@orcl internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting orcl_1211@orcl Internal Concurrent Manager -- shell process ID 21954618
          logfile=/apps/applmgr/orclcomn/admin/log/orcl_career1/orcl_1211.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=60 (default)
             pmon=20 (default)
           quesiz=1 (default)
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 11-DEC-2013 14:47:57 -
Shutting down Internal Concurrent Manager : 11-DEC-2013 14:47:57
List of errors encountered:
_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The orcl_1211@orcl internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting orcl_1211@orcl Internal Concurrent Manager -- shell process ID 17826000
          logfile=/apps/applmgr/orclcomn/admin/log/orcl_career1/orcl_1211.mgr
          PRINTER=noprint
           mailto=applmgr
          restart=N
             diag=N
            sleep=60 (default)
             pmon=20 (default)
           quesiz=1 (default)
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 11-DEC-2013 15:17:50 -
Shutting down Internal Concurrent Manager : 11-DEC-2013 15:17:50
List of errors encountered:
_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The orcl_1211@orcl internal concurrent manager has terminated with status 1 - giving up.
------- end out put

How to up concurrent manager in R12 EBS installation in windows 2003 server

Hi,
I have installed R12 EBS on windows 2003 server. It was working fine for 2 days.
Then suddenly when I submitted some concurrent program ,
status was "No Manager" i.e. concurrent manager was down.
I dont know how to restart/start concurrent manager .
Any help will be greatly appreciated .
Thanks

Thanks hussein , where do I get application env file. I tried stoping cm from the services and then executed file CMCLEAN.sql and then restarted cm from services menu. However still I can't see cm running in application. I bounced the server also before restartingConfiguration and Environment Files
http://docs.oracle.com/cd/E18727_01/doc.121/e13676/T530334T530337.htm#admu-cef
Did you commit the changes after running cmclean.sql? If yes, please check the CM log file for any errors.
Thanks,
Hussein

Concurrent manager hands

Dear all,
Recently I'm facing weird situation.
Suddenly the concurrent manager hangs. It doesn't show "Inactive Manager"
It just doesn't progress. It stays on "Pending Normal"
Neither a restart of the CM, nor restart of the whole application (and the DB) is enough.
I had to reboot the server in order the CM work properly.
This issue is recurring on a daily basis.
Could you help me in solving it
Your prompt reply is highly appreciated
Rgds,
wazwaz

Hi,
Check the following:
1. run the "purge Concurrent requests" for all schema's and age will be around 15 days as the parameter
2. try to remove unwanted logfiles under $APPLCSF/$APPLLOG as well as $APPLCSF/$APPLOUT for out files
3. monitor the concurrent manager log files under $APPLCSF/$APPLLOG
(preferably the file name looks like <Instance>hostname.mgr (for example PRODserver1.mgr).
4. check the rows in the FND_CONCURRENT_REQUESTS and try to reduce it (if above Item1 Doesn't reduce much rows, You need to consider to purge the rows in this table)
5. try to run the cmclean.sql which available in the metalink. Please stop the concurrent manager before run this sql query
6. Are all the concurrent request changed into pending:normal? I mean, whenever we submit the requests all the requests getting pending:Normal?
regards,
Pandian

Concurrent Manager not starting after patching/ cloning

Hi,
We have an issue where after cloning and/or patching an environment the concurrent manager doesn't start. Our steps to resolve this problem have thus far been as follows:
1. Apply 3830807
2. Run autoconfig
3. Run cmclean.sql on environment
4. Check the libc* files in 8.0.6 ORACLE_HOME/lib/stubs
We had an instance after a patch was applied where the conc mgr did not start and we applied all of the above, in that order. No success. We then decided to apply the 3830807 patch again and run autoconfig- basically re- run steps 1 and 2. Success. In another instance, running the cmclean.sql resolved the error. In some instances, simply shutting down the application and DB and restarting will be enough.
Our problem is that the resolution to this error always seems random. What may work in one instance almost never works in another. Additionally, the problem has started since we've applied ATG RUP 6 to our LIVE environment and our clones. Coincidence?
We have logged an SR but I feel like we're being spun in circles- I'm not getting a direct answer or resolution path from them.
If someone could provide some guidance on a proper resolution path for this conc mgr issue I would very much appreciate it.
Thanks,
Lia.

Basically the approach we're now taking (and that's working) is that after applying a patch, or set of patches, we apply patch 3830807 and then run autoconfig on the db and apps tier. We then shut down the application (if not already down) and the database and then bring everything back up.
Thanks to all for their assistance.
Lia.

Unable to start concurrent manager Service on WinXP

Hi
I have successfully installed R12 vision instance on widows XP with service pack 3.when i try to start oracle concurrent manager service from windows services it gives me error
The oracleConcMgrVIS_demo (demo is the name of computer) service on local computer started then stopped. Some services started stop automatically if they have no work to for examples the performance logs and alert services.
I am not able to run any report or concurrent request bcz of this.
Kindly help me.
Regards

Hi ,
Please go to services and update CM services properties.
Right manager services--> Properties-->Log On--> As a domain User.( Not Local Usre)
Restarte the machine with below command (Don't start from start->shutdown)
Go to command prompt-- type below command
shutdown -r -t 0 1
l

Concurrent manager not working

Hi all
I have just been assigned to work on an environment that was just installed by someone else .
The problem is that when I submit a new request to the concurrent manager it stops in the phase "inactive" and the message in the status is " No manager"
I restarted the services using the adstpall/adstrtal scripts and the problem is still not fixed . I also tried to restart the service 'concmgrvis_hostname' and it still not working . Is there any way I can fix the problem other than a fresh install. Keep in mined I do not know what the person who installed it did ,or if he knows what he is doing
Thanks in advance

Please review the CM log file, make sure that no error/warning messages are reported. I would suggest you run cmclean.sql and check then.
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

R12 on Windows XP - Concurrent Manager Service

I installed R12 on WIndows XP.
It is working fine, but concurrent Manager Service is not getting created.
I tried with Auto Config...and also running directly ccmsvc.exe...
It always errors out displaying a window which reads Oracle Applications Concurrent Manager service encountered an error and needs to close. We are sorry for inconvenience.+
I looked at the Application log in Event viewer. It says Application: ccmsvc.exe and faulting module ntdll.dll.
Does any body know how to fix the faulting module ntdll.dll error....?
THanks in Advance
Ambati

Sorry for the delay...I was sick all these days....
I did restart the machine.....
THis is the error report in event viewer...and the version of ntdll.dll appears to be 5.1.2600.5512
Faulting application ccmsvc.exe, version 0.0.0.0, faulting module ntdll.dll, version 5.1.2600.5512, fault address 0x000249ab.+
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.+
I have Windows XP Service Pack 3 installed on my machine.

Concurrent manager restart

Similar Messages

Maybe you are looking for