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

Similar Messages

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

  • 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

  • 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

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

  • Concurrent Manager not started after Clonning - Forms not showing

    Hi,
    I have cloned PROD system into a TEST system using Rapid Clone.
    After I started TEST services, I log into application but OracleForms are not working. When I click on a function which calls a selfservice form, it works well, but when the function calls an Oracle form, the Forms Environment is opened but there is only "Window" menu (which contains "tile", "cascade", etc).
    The same situation even when I open directly from http://apptest.rmis:8000/dev60cgi/ifcgi60.exe.
    Also Concurrent Manager service is not started. I deleted and recreated it, ran autoconfig, but the problem still persist.
    Please help me to solve the issue.
    Thank you.

    Hi,
    I did the relinking of all executables under FND, tried to adsvcm -deinstall (-install) and ran autoconfig successfully, but still CM service is started than stopped.
    Here is the CM logfile:
    The Internal Concurrent Manager has encountered an error.
    Review concurrent manager log file for more detailed information. : 15-FEB-2008 16:33:27 -
    Shutting down Internal Concurrent Manager : 15-FEB-2008 16:33:27
    Reviver is not enabled, not spawning a reviver process.
    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-12222: TNS:no such
    protocol adapter
    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.
    Please help to solve this issue.
    Thank you.

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

  • 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

  • R12 Staging in Linux (Autostage is not picking up from next dvd)

    Hi,
    I am doing the autostage using perl.
    How to do?
    anyone give - step by step in details.
    Thanks in advance
    Regs.
    TS

    Duplicate thread (Please post only once):
    R12 Staging in Linux (Autostage is not picking up from next dvd)
    R12 Staging in Linux (Autostage is not picking up from next dvd)

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

  • Concurrent Manager not processing the requests

    Dear friends,
    We are facing a serious issue with our production instance since morning.
    The concurrent managers are not processing the requests. As its month closing, a lot of requests are being piled up in the Standard Manager's queue.
    The Standard Manager is up. We have verified that by the processes at OS and Concurrent Manager Administer form as well.
    The Conc Manager Admin form shows:
    Actual process: 50
    Target Process 50:
    Running Requests: 50
    Pending Requests: 304
    However, when we check from Concurrent Requests form by selecting Status=Normal, Phase=Running, its showing only 6 requests as running and rest all in pending phase.
    These requests are running for long and no other requests seem to being picked up by the CM.
    an urgent help is required as its production environment and all the users are complaining.
    Thanks.

    Its R12.1.1 Apps with 11.1.0.7 DB
    We have found the issue. In the Concurrent Manager Administer form, when we clicked on the Requests Button, it shows a lot of the following requests:
    Check Event Alert - ALECTC
    This request is not shown in Concurrent Requests form.
    We found that the Alert mails were not being sent. At OS level, we found 50 ALECTC OS processes were running.
    We killed those and immediately Standard Manager started picking up the pending requests.
    I am not yet sure of ALECTC processes. Can someone explain ???
    Thanks.

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

Maybe you are looking for