Internal Concurrent Manager deactivated.

Hi
Iam working on setting up R12 instances on Amazon Cloud Virtual machines.
After running post clone steps when I check the concurrent managers - manage screen I see old node name. How to update this with the new node name.
Also after changing the node name the internal concurrent manager is in deactivated state, How to get this activated.
Pls let me know how to resolve the issue.
Sree

After running post clone steps when I check the concurrent managers - manage screen I see old node name. How to update this with the new node name. You can update TARGET_NODE column in FND_CONCURRENT_QUEUES table from the backend.
Also after changing the node name the internal concurrent manager is in deactivated state, How to get this activated. From the application (as mentioned above by Taher) or stop/start the CM using adcmclt.sh script.
Thanks,
Hussein

Similar Messages

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

How to check Internal, Concurrent Manager status in Oracle Apps R12 from fr

Step by step how to check Internal, Concurrent Manager status in Oracle Apps R12 from front end and how to start them.

Richa wrote:
Step by step how to check Internal, Concurrent Manager status in Oracle Apps R12 from front end Concurrent Processing - Concurrent Manager Generic Platform Questions and Answers [ID 105133.1]
and how to start them1) Using adcmctl.sh (from the backend)
2) Using Activate button (from the front-end) -- http://docs.oracle.com/cd/E18727_01/doc.121/e12893/T174296T174302.htm#4334248
Thanks,
Hussein

Internal Concurrent Manager status could not be determined

Hi Experts,
After installation of EBS 12.1.1 we got above error
"Internal Concurrent Manager status could not be determined"
while starting CM. and form are not open getting error
"FRM -92101 there was a failure in the form server durring startup."
Please help.
thanks in advance.

Hi Experts,
after compile JSP pages i got error in log file as
[13931] translating: 17s elapsed, 200 successful 0 failed
[13932] translating: 18s elapsed, 200 successful 0 failed
[13931] translating: 18s elapsed, 200 successful 0 failed
[13932] translating: 26s elapsed, 200 successful 0 failed
[13931] translating: 30s elapsed, 200 successful 0 failed
[13932] !!TRANSLATION ERROR(0) pvxPrtnrRelLOVMain.jsp:
[13932] !!TRANSLATION ERROR(0) amsProdCreatMain.jsp:
[13931] !!TRANSLATION ERROR(0) iecalgrelcontrollist.jsp:
[13932] !!TRANSLATION ERROR(0) asfAdminQuotaLOVMain.jsp:
[13931] !!TRANSLATION ERROR(0) pvxEnrlReprtParamMain.jsp:
[13931] !!TRANSLATION ERROR(0) csfwctrc.jsp:
[13932] !!TRANSLATION ERROR(0) jtfutc.jsp:
[13931] !!TRANSLATION ERROR(0) jtfDpfFlowSteps.jsp:
[13932] !!TRANSLATION ERROR(0) amsTargetGroupDtailMain.jsp:
[25393] could not delete /u01/VISION/apps/apps_st/comn/_pages/_cabo/_jsps/_gr.java
[25393] !!COMPILATION ERROR(0) cabo/jsps/gr.jsp:
javac: file not found: cabo/jsps/_gr.java
Usage: javac <options> <source files>
use -help for a list of possible options
[25393] could not delete /u01/VISION/apps/apps_st/comn/_pages/_jsp/_wf/_WFNtfDetails.java
[25393] !!COMPILATION ERROR(0) jsp/wf/WFNtfDetails.jsp:
javac: file not found: jsp/wf/_WFNtfDetails.java
Usage: javac <options> <source files>
use -help for a list of possible options
[25393] could not delete /u01/VISION/apps/apps_st/comn/_pages/_jsp/_fnd/_aolj__framework__agent.java
COMPILED: 5973 [failed: 556] in 7m58s
13903 FINISHING Mon Mar 26 05:42:23 2012
Please help.
Thanks,
Mohammad

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

The Internal Concurrent Manager has encountered an error.

Routine &ROUTINE has attempted to start the internal concurrent manager. The ICM is already running. Contact you system administrator for further assistance.afpdlrq received an unsuccessful result from PL/SQL procedure or function FND_DCP.Request_Session_Lock.
Routine FND_DCP.REQUEST_SESSION_LOCK received a result code of 1 from the call to DBMS_LOCK.Request.
Possible DBMS_LOCK.Request resultCall to establish_icm failed
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 06-JUN-2012 00:51:22 -
Shutting down Internal Concurrent Manager : 06-JUN-2012 00:51:22
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 PPD_0606@PPD internal concurrent manager has terminated with status 1 - giving up.
Edited by: sahil jain on Jun 6, 2012 10:10 PM

Hi;
1. What is EBS version?
2. Did you check:
Concurrent Managers Will Only Start on One Node in PCP/RAC Environment [ID 264296.1]
Concurrent Processing - The Concurrent Manager Fails to Start on GSM Enabled Due to DBMS_LOCK.Request ResultCall Failed to Establish ICM [ID 245563.1]
Regard
Helios

Internal concurrent manager is not active in R12.1.3

hi,
i have R12.1.3 installed on guest OEL 5.5.
my concurrent manager is down.
here is the output of adcmctl,
when i start using the above utility, ICM becomes active but after a min it again goes back to inactive status.
it would be great if someone can help me on bringing this up.
regards,
ad
adcmctl.sh status apps/apps
You are running adcmctl.sh version 120.17.12010000.5
Internal Concurrent Manager is Not Active at this time.
adcmctl.sh: exiting with status 0
adcmctl.sh: check the logfile /u01/oracle/VIS/inst/apps/VIS_localhost/logs/appl/admin/log/adcmctl.txt for more information ...

thanks Hussain.
i see following in the CM log,
please advice.
thanks,
========================================================================
Starting VIS_0519@VIS Internal Concurrent Manager -- shell process ID 15416
logfile=/u01/oracle/VIS/inst/apps/VIS_localhost/logs/appl/conc/log/VIS_0519.mgr
PRINTER=noprint
mailto=oracle
restart=N
diag=N
sleep=30
pmon=4
quesiz=1
Reviver is ENABLED
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 19-MAY-2013 11:43:50 -
Shutting down Internal Concurrent Manager : 19-MAY-2013 11:43: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 VIS_0519@VIS internal concurrent manager has terminated with status 1 - giving up.

Internal concurrent manager is 0

After completion of cloning, internal manager is 0.,but other managers are 1and 1.,can anyone help me?

vaaru wrote:
After completion of cloning, internal manager is 0.,but other managers are 1and 1.,can anyone help me?Please do the following:
- Stop the CM
- Purge FND_NODES table then run AutoConfig on all tier nodes -- How to get a clean Autoconfig Environment ? [ID 391406.1]
- Run cmclean.sql script -- Concurrent Processing - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]
- Start the CM
If you still have the same issue, please check the contents of the CM log file.
Thanks,
Hussein

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
---------------------------------------------------------------------------

R12.1.3 internal concurrent manager not running (upgraded from 11.5.10.2)

I have an instance that I have upgraded from 11.5.10.2 --> 12.1.1 --> 12.1.3 (db is 10.2.0.4)
oldservername CRMTESTAPP (still machine name)
newservername CRMR12 (alias in DNS and hosts to same machine)
After doing the upgrade I ran into an issue where the hostname.domainname was 31 characters long, which created an issue trying to start the ICM due to column limits in FND_CONCURRENT_PROCESSES (doc 413164.1)
We created an alias to the server that was shorter and I ran the adcfgclone to configure the instance with the new server name.
Everything ran, completed and the ICM will still not start. It seems to be looking for the FNDFS_oldservername instead of using the newservername
in FND_NODES only the newservername and authentication are listed. I shut everything down, ran cmclean.sql and I have also tried the CM Recovery wizard.
In OAM when you click the ICM, and click Edit it shows the newservername as the only node listed, yet still when you click Log you get:
"An error occurred while attempting to establish an Applications File Server connection with the node FNDFS_CRMTESTAPP. There may be a network configuration problem, or the TNS listener on node FNDFS_CRMTESTAPP may not be running. Please contact your system administrator."
Also when I click Internal Manager, then click the Environment button it seems to be referencing the old 11.5.10 install directories instead of the new ones.
How can I define which server the instance needs to use other than the methods I have tried?
Thanks

None of the env files reference the old host
What about other CMs?
All are defined as the correct node
Can you find any errors in the CM log file?
None other than the 30 chararcter limit error.
If the internal manager shows the correct hostname, then you should find it in the table. For now, take a backup of this table, and update the target_node column for all CMs and try again.
I have updated the table, however it doesn't make a difference because none of the other CM will run without the ICM running according to their diagnostic logs.
I was looking through document 413164.1 and noticed it said that hostname / domainname has to be less than 30 characters. Is this to say hostname has to be less than 30 AND domainname has to be less than 30 OR hostname.domainname together have to be less than 30?
I also looked on our current 11.5.10.2 instance which has the same 30 character limit on the node_name column in fnd_concurrent_queues and it only populates with hostname. Which I assume is what R12 would do as well, which means I am well under the 30 character limit for just node_name.
Is there something I can trace to see what the insert statement is trying to put into the node_name column? The ICM according to OAM is still configured to point to the old 11.5.10 home as opposed to the new 12 home? Autoconfig files have nothing to reference the old home that I have found, where does the ICM pull the environment settings from?
Thanks again

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

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

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

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

Concurrent Manager not starting automatically with adstrtal.sh apps/apps

I am facing an issue with ICM, its not starting automatically when I start the application with help of
/d01/oracle/viscomn/admin/scripts/VIS_oracleapps/adstrtal.sh apps/apps
But, I am able to start it manually with adcmctl.sh start apps/apps - any clue why its not starting automatically?
Pls let me know if any suggestions to troubleshoot...
CM log file snip -
Shutting down Internal Concurrent Manager : 26-JUN-2008 11:06:13
List of errors encountered:
_ 1 _
Routine AFPCMT encountered an ORACLE error. ORA-01012: not logged on
Review your error messages for the cause of the error. (=<POINTER>)
_ 2 _
Routine AFPCSQ encountered an ORACLE error. ORA-01017: invalid
username/password; logon denied
Review your error messages for the cause of the error. (=<POINTER>)
The VIS_0626@VIS internal concurrent manager has terminated with status 1 - giving up.
Thanks,
Ambi

This issue has been fixed, it was due to (apps) password was misspelt in the script calling the adstrtal.sh script.

Concurrent manager problem on Cloud

Hi
I did the clone on cloud machine.
Iam getting issues with concurrent manager.Below is the error in the log file.
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-MAY-2011 03:29:04 -
Shutting down Internal Concurrent Manager : 07-MAY-2011 03:29:04
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 12899 in insert_icm_record
Cause: insert_icm_record failed due to ORA-12899: value too large for column "APPLSYS"."FND_CONCURRENT_PROCESSES"."NODE_NAME" (actual: 31, maximum: 30).
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, :mgrusrid2, :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.
sh: line 63: mail: command not found
The DEMO_0507@DEMO internal concurrent manager has terminated with status 1 - giving up.
[root@domU-12-q1-39-1A-05-F3 log]# hostname
domU-12-3q-39-1A-05-F3.compute-1.internal
SQL> select node_name from fnd_nodes;
NODE_NAME
AUTHENTICATION
RDCORACLEAPP
RDCORACLEDB
Where does this get the hostname or node name from.
Pls help.
Sree

Where does this get the hostname or node name from.From the hosts file and from the source instance that you have cloned from -- Concurrent Managers Fail To Start After New Install of Release 12 [ID 413164.1]
Please purge FND_NODES table as per (Concurrent Processing - Steps To Clean Nonexistent Nodes or IP Addresses From FND_NODES [ID 260887.1]) and after correcting all the entries in the hosts file, and check then (make sure you run AutoConfig on the database/application tier nodes).
Thanks,
Hussein

Concurrent Manager: Service Manager AUTHENTICATION

Hi hussein/helios
I navigate to System Administrator > Concurrent > Manager > Administer >
I checked :
Concurrent Manager: Service Manager AUTHENTICATION actual = 1; but target = 0; and Status = Target node/queue unavailable
How do I resolve this issue?
Thanks a lot
Ms K

Hi,
Please see these documents.
Note: 353031.1 - Why Does "Internal Concurrent Manager found node AUTHENTICATION to be down" Error Appear in Log?
Note: 342939.1 - What is the AUTHENTICATION Node and How is it Related to 'Could Not Contact Service Manager FNDSM_AUTHENTICATION_PROD' Message
Thanks,
Hussein

Internal Concurrent Manager deactivated.

Similar Messages

Maybe you are looking for