Concurrent managers not getting up

When running concurrent request for active user the phase is Inactive and the status is No manager

01/04/12-17:02:48 :: You are running adcmctl.sh version 120.14.12000000.4
01/04/12-17:02:48 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/04/12-17:02:48 :: adcmctl.sh: exiting with status 0
=======================================================================
01/04/12-17:03:24 :: You are running adcmctl.sh version 120.14.12000000.4
01/04/12-17:03:24 :: adcmctl.sh: Shutting down concurrent managers for PROD ...
ORACLE Password:
Submitted request 325204 for CONCURRENT FND SHUTDOWN
01/04/12-17:03:26 :: adcmctl.sh: exiting with status 0
=======================================================================
01/04/12-17:19:44 :: You are running adcmctl.sh version 120.14.12000000.4
01/04/12-17:19:44 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/04/12-17:19:44 :: adcmctl.sh: exiting with status 0
=======================================================================
01/04/12-17:38:59 :: You are running adcmctl.sh version 120.14.12000000.4
01/04/12-17:38:59 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/04/12-17:38:59 :: adcmctl.sh: exiting with status 0
=======================================================================
01/04/12-17:54:54 :: You are running adcmctl.sh version 120.14.12000000.4
01/04/12-17:54:54 :: adcmctl.sh: Shutting down concurrent managers for PROD ...
ORACLE Password:
Submitted request 325211 for CONCURRENT FND SHUTDOWN
01/04/12-17:54:55 :: adcmctl.sh: exiting with status 0
=======================================================================
01/05/12-07:21:36 :: You are running adcmctl.sh version 120.14.12000000.4
01/05/12-07:21:37 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/05/12-07:21:37 :: adcmctl.sh: exiting with status 0
=======================================================================
01/05/12-13:03:47 :: You are running adcmctl.sh version 120.14.12000000.4
01/05/12-13:03:47 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/05/12-13:03:48 :: adcmctl.sh: exiting with status 0
=======================================================================
01/05/12-13:04:29 :: You are running adcmctl.sh version 120.14.12000000.4
01/05/12-13:04:29 :: adcmctl.sh: Shutting down concurrent managers for PROD ...
ORACLE Password:
Submitted request 326212 for CONCURRENT FND SHUTDOWN
01/05/12-13:04:34 :: adcmctl.sh: exiting with status 0
=======================================================================
01/05/12-13:05:39 :: You are running adcmctl.sh version 120.14.12000000.4
01/05/12-13:05:39 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/05/12-13:05:39 :: adcmctl.sh: exiting with status 0
=======================================================================
01/05/12-14:52:05 :: You are running adcmctl.sh version 120.14.12000000.4
01/05/12-14:52:05 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/05/12-14:52:05 :: adcmctl.sh: exiting with status 0
=======================================================================
01/05/12-14:52:16 :: You are running adcmctl.sh version 120.14.12000000.4
01/05/12-14:52:16 :: adcmctl.sh: Shutting down concurrent managers for PROD ...
ORACLE Password:
Submitted request 327212 for CONCURRENT FND SHUTDOWN
01/05/12-14:52:34 :: adcmctl.sh: exiting with status 0
=======================================================================
01/05/12-14:53:16 :: You are running adcmctl.sh version 120.14.12000000.4
01/05/12-14:53:16 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/05/12-14:53:16 :: adcmctl.sh: exiting with status 0
=======================================================================
01/05/12-15:15:16 :: You are running adcmctl.sh version 120.14.12000000.4
01/05/12-15:15:16 :: adcmctl.sh: Shutting down concurrent managers for PROD ...
ORACLE Password:
Submitted request 327215 for CONCURRENT FND SHUTDOWN
01/05/12-15:15:16 :: adcmctl.sh: exiting with status 0
=======================================================================
01/05/12-15:17:59 :: You are running adcmctl.sh version 120.14.12000000.4
01/05/12-15:18:00 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/05/12-15:18:00 :: adcmctl.sh: exiting with status 0
=======================================================================
01/06/12-07:58:28 :: You are running adcmctl.sh version 120.14.12000000.4
01/06/12-07:58:28 :: adcmctl.sh: Shutting down concurrent managers for PROD ...
ORACLE Password:
Submitted request 327216 for CONCURRENT FND SHUTDOWN
01/06/12-07:58:30 :: adcmctl.sh: exiting with status 0
=======================================================================
01/06/12-08:03:37 :: You are running adcmctl.sh version 120.14.12000000.4
01/06/12-08:03:37 :: adcmctl.sh: Shutting down concurrent managers for PROD ...
ORACLE Password:
Submitted request 327217 for CONCURRENT FND SHUTDOWN
01/06/12-08:03:37 :: adcmctl.sh: exiting with status 0
=======================================================================
01/06/12-08:17:02 :: You are running adcmctl.sh version 120.14.12000000.4
01/06/12-08:17:02 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/06/12-08:17:02 :: adcmctl.sh: exiting with status 0
=======================================================================
01/06/12-08:34:10 :: You are running adcmctl.sh version 120.14.12000000.4
01/06/12-08:34:10 :: adcmctl.sh: Shutting down concurrent managers for PROD ...
ORACLE Password:
Submitted request 327223 for CONCURRENT FND SHUTDOWN
01/06/12-08:34:10 :: adcmctl.sh: exiting with status 0
=======================================================================
01/06/12-08:42:35 :: You are running adcmctl.sh version 120.14.12000000.4
01/06/12-08:42:36 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/06/12-08:42:36 :: adcmctl.sh: exiting with status 0
=======================================================================
01/06/12-09:06:55 :: You are running adcmctl.sh version 120.14.12000000.4
01/06/12-09:06:55 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/06/12-09:06:55 :: adcmctl.sh: exiting with status 0
=======================================================================
01/06/12-09:20:08 :: You are running adcmctl.sh version 120.14.12000000.4
01/06/12-09:20:09 :: adcmctl.sh: Shutting down concurrent managers for PROD ...
ORACLE Password:
Submitted request 327228 for CONCURRENT FND SHUTDOWN
01/06/12-09:20:09 :: adcmctl.sh: exiting with status 0
=======================================================================
01/06/12-09:44:29 :: You are running adcmctl.sh version 120.14.12000000.4
01/06/12-09:44:29 :: adcmctl.sh: Starting concurrent manager for PROD ...
01/06/12-09:44:29 :: adcmctl.sh: exiting with status 0
=======================================================================

Similar Messages

  • Concurrent managers not processing requests

    Hi,
    Today I met with a strange issue. My concurrent managers are up and running/there is no errors written in alert.log file on db node.
    But when when I submit any request then it is not getting proceed. it gets Pending/Normal status. and there is no other request which is currently running in system.
    I stopped Internal concurrent manager using adcmctl.
    I ran cmclean.sql then tried to resubmit request. but still I am getting same status.
    Can anyone please help me ASAP.
    Thanks in advance.
    Nish

    Today I met with a strange issue. My concurrent managers are up and running/there is no errors written in alert.log file on db node.Please post the details of the application release, database version and OS.
    But when when I submit any request then it is not getting proceed. it gets Pending/Normal status. and there is no other request which is currently running in system.
    I stopped Internal concurrent manager using adcmctl.
    I ran cmclean.sql then tried to resubmit request. but still I am getting same status.
    Can anyone please help me ASAP.What about the CM log file?
    Please bounce the database/application services and check then.
    Thanks,
    Hussein

  • Concurrent Managers Not coming up after applying a patch on 11.5.9.2

    Hi,
    I see below error on CM log.
    Could not start Service Manager FNDSM_IP_uat. The TNS alias could not be located, the listener process on IP could not be contacted, or the listener failed to spawn the Service Manager process.
    Routine AFPEIM encountered an error while starting concurrent manager PASMGR with library /u01/appluat/uatappl/pa/11.5.0/bin/PALIBR. Check that your system has enough resources to start a concurrent manager process. Contact your system adm : 19-FEB-2013 19:13:25 Process monitor session ended : 19-FEB-2013 19:13:25
    Check that your system has enough resources to start a concurrent manager process. Contact your system adm
    tnsping FNDSM_IP_uat is fine, i tried cmclean.sql and bouncing db and apps tiers, no use.
    I have checked Concurrent Processing - Routine AFPEIM Encountered an Error While Starting Concurrent Manager [ID 783263.1],
    but it is for 11.5.10.2.
    Please suggest.
    Thanks,

    kkrm333 wrote:
    I am able to solve the issue by applying Patch 3830807: PATCH 3293983 NEEDS TO INCLUDE ALL THE MAKEFILES UNDER THE 8.0.6 ORACLE_HOME as per m note Concurrent Manager Fails To Start With Error 'Could not start Service Manager FNDSM_<server>_<SID>' Error [ID 423170.1]
    Thanks,Thanks for the update and for sharing the solution!
    Regards,
    Hussein

  • All concurrent managers will not start

    We installed the minimum baseline patches for 11.5.10.2 along with the July CPU patches. After doing that, the standard manager (fndlibr) starts but all of the specialized managers do not (invlibr). We have relinked everything, run cmclean.sql, shortened the system path variable, etc. without success. This is on windows. I am looking for suggestions on what else to try.

    Here's the script. Already tried setting the environment variable and all that does is echo the setting of the environment commands. Notice the script also says can just start the service.
    @echo OFF
    @if not "%ORAWIN_DBG%"=="" echo %ORAWIN_DBG%
    @REM $Header: adcmctl_nt.cmd 115.19 2009/03/20 09:07:36 jmajumde ship $
    @REM *========================================================================+
    @REM | Copyright (c) 2000 Oracle Corporation, Redwood Shores, California, USA |
    @REM | All rights reserved |
    @REM | Applications Division |
    @REM +========================================================================+
    @REM |
    @REM | FILENAME
    @REM | adcmactl.cmd
    @REM |
    @REM | DESCRIPTION
    @REM | Start / Stop Concurrent Manager for orat_rta08
    @REM |
    @REM | USAGE
    @REM | adcmactl.cmd start <APPS username/APPS password>
    @REM |
    @REM | PLATFORM
    @REM | NT Generic
    @REM |
    @REM | NOTES
    @REM | On NT you can start and stop the concurrent manager process using the
    @REM | services utility in the control panel.
    @REM |
    @REM | HISTORY
    @REM |
    @REM +========================================================================+
    @REM
    REM ###############################################################
    REM
    REM This file is automatically generated by AutoConfig. It will be read and
    REM overwritten. If you were instructed to edit this file, or if you are not
    REM able to use the settings created by AutoConfig, refer to Metalink document
    REM 165195.1 for assistance.
    REM
    REM ###############################################################
    @REM
    echo
    if "%ORAWIN_DBG%"=="ON" echo You are running adcmctl.cmd
    echo
    @REM Get Date and Time
    FOR /F "DELIMS=" %%a IN ('DATE /T') DO (
    SET dateline=%%a
    FOR /F "DELIMS=" %%a IN ('TIME /T') DO (
    SET timeline=%%a
    echo %dateline%%timeline%
    set env_file="f:\oracle\orapappl\APPSorat_rta08.cmd"
    if exist %env_file% goto env_ok
    echo Cannot find environment file %env_file%
    VERIFY OTHER 2> NUL
    goto end
    :env_ok
    call %env_file%
    IF "%1" == "" GOTO usage
    set control_code=%1
    setlocal enableextensions
    if "%2" == "" (
    set /P unpw="Enter the APPS Username/Password: "
    ) else (
    if "%2" == "-nopromptmsg" (
    set /P unpw=""
    ) else (
    set unpw=%2
    for /F "usebackq tokens=1,2 delims=/" %%i in ('%unpw%') do set APPS_UNAME=%%i && set APPS_PWD=%%j
    IF NOT EXIST f:\oracle\orapcomn\admin\log\orat_rta08 mkdir f:\oracle\orapcomn\admin\log\orat_rta08
    REM
    REM Check Reviver pid file
    REM
    set CMPIDFILE="f:\oracle\orapappl\fnd\11.5.0\log\reviver_orat_rta08.pid"
    if exist %CMPIDFILE% goto :get_pidfile
    REM As we are providing the functionality to check the status via bug 3835198.
    REM The following line may be conflicting .So commenting it.
    REM echo Concurrent managers (no pid file) not running
    set RUNNING=0
    goto :reviver_cont
    :get_pidfile
    FOR /F %%a IN ('type %CMPIDFILE%') DO (
    set reviver_pid=%%a
    IF "x%reviver_pid%" == "x" (
    echo Concurrent managers ( %reviver_pid% ) not running
    set RUNNING=0
    ) ELSE (
    echo Concurrent managers ( %reviver_pid% ) is running
    set RUNNING=1
    :reviver_cont
    REM
    REM check to see the status and set to 1 if started
    REM
    SET status=0
    FOR /F "delims=" %%a IN ('NET START ^| findstr /C:"OracleConcMgrorat_rta08"') DO (
    SET status=1
    IF /i "%control_code%" == "status" GOTO control_ok
    IF /i "%control_code%" == "start" GOTO control_ok
    IF /i "%control_code%" == "stop" GOTO control_ok
    echo
    echo $program: You must either specify 'start' or 'stop' or 'status'
    goto usage
    :control_ok
    IF /i "%control_code%" == "status" GOTO statuscm
    IF /i "%control_code%" == "start" GOTO startcm
    IF /i "%control_code%" == "stop" GOTO stopcm
    :statuscm
         IF %status% == 0 (
    ECHO The service "OracleConcMgrorat_rta08" hasn't been started
    GOTO :end
    IF %status% == 1 (
    ECHO The service "OracleConcMgrorat_rta08" is already started
    GOTO :end
    :startcm
    IF %status% == 1 (
    ECHO The service "OracleConcMgrorat_rta08" is already started
    GOTO :end
    echo Starting concurrent manager for %DB_NAME% ...
    net start OracleConcMgrorat_rta08
    goto end
    :stopcm
    IF %status% == 0 (
    ECHO The service "OracleConcMgrorat_rta08" hasn't been started
    GOTO :end
    IF %RUNNING% == 0 goto :disable_rev
    IF %RUNNING% == 1 (
    f:\oracle\orapappl\fnd\11.5.0\bin\reviver.exe -k %reviver_pid%
    DEL /Q %CMPIDFILE%
    :disable_rev
    echo Shutting down concurrent managers for %DB_NAME% ...
    ( echo %APPS_PWD% ) | f:\oracle\orapappl\fnd\11.5.0\bin\concsub.exe %APPS_UNAME% SYSADMIN "System Administrator" SYSADMIN WAIT=Y CONCURRENT FND DEACTIVATE > f:\oracle\orapcomn\admin\log\orat_rta08\adcmctl.txt 2>&1
    goto end
    :usage
    echo Usage:
    echo adcmctl.cmd {start^|stop^|status} ^<APPS username/APPS password^>
    echo
    VERIFY OTHER 2> NUL
    :end
    echo adcmctl.cmd exiting with status %ERRORLEVEL%

  • Not able to start the concurrent Managers in Release 12 on Redhat Linux 4

    Hi,
    I was able to successfully install Release 12 Vision on Other than Linux.. Every thing is working fine but concurrent managers are not active except the Internal Manager. Rest of the Managers has no value in the node name field and the status is "Target node/queue unavailable".. I also ran adcmcmtl.sh to manually stop and start the managers but still facing the same issue.. Other than the install, i have not applied any patches..
    Please tell me what i'm missing..
    Thanks in Advance,
    Prasad

    Check the CM log file for any errors.
    Have you tried to recover the CM from OAM? Shutdown the CM first and run this step.

  • Concurrent timers are not getting invoked for same timer inf

    Do weblogic has some parameter in weblogic deployment descriptor like numAlarmThreads="5" minThreads="1" maxThreads="10" etc
    becoz I am facing one problem relating to timer service in EJB
    Problem Scope: Concurrent timers are not getting invoked for same timer info (Serializable object containing the details of timer).
    Details : I am implementing EJB timer 2.1 and when ejbTimeOut execution of one timer exceeds the interval time, next timeout doesn’t happens till the execution of first ejbTimeOut completes . Ideally the timers should behave in the manner that on every interval the ejbTimeOut should occur no matter the previous timeout is completed or not
    for example : consider there is timer T whose timeout occurs every minute, and on every timeout it calls process P, so on every minute ideally container should give call to process P irrespective of the previous status of P (call is complete or not). In our case next call to process P is not happening after timeout also since it is waiting for previous call to P to get completed

    You should also cross-post this in the WebLogic EJB forum:
    WebLogic Server - EJB

  • Concurrent timers are not getting invoked for same timer info (Serializable

    Problem Scope: Concurrent timers are not getting invoked for same timer info (Serializable object containing the details of timer).
    Details : I am implementing EJB timer 2.1 and when ejbTimeOut execution of one timer exceeds the interval time, next timeout doesn’t happens till the execution of first ejbTimeOut completes . Ideally the timers should behave in the manner that on every interval the ejbTimeOut should occur no matter the previous timeout is completed or not
    for example : consider there is timer T whose timeout occurs every minute, and on every timeout it calls process P, so on every minute ideally container should give call to process P irrespective of the previous status of P (call is complete or not). In our case next call to process P is not happening after timeout also since it is waiting for previous call to P to get completed

    You should also cross-post this in the WebLogic EJB forum:
    WebLogic Server - EJB

  • Concurrent timers are not getting invoked for same timer info

    Problem Scope: Concurrent timers are not getting invoked for same timer info (Serializable object containing the details of timer).
    Details : I am implementing EJB timer 2.1 and when ejbTimeOut execution of one timer exceeds the interval time, next timeout doesn’t happens till the execution of first ejbTimeOut completes . Ideally the timers should behave in the manner that on every interval the ejbTimeOut should occur no matter the previous timeout is completed or not
    for example : consider there is timer T whose timeout occurs every minute, and on every timeout it calls process P, so on every minute ideally container should give call to process P irrespective of the previous status of P (call is complete or not). In our case next call to process P is not happening after timeout also since it is waiting for previous call to P to get completed

    You should also cross-post this in the WebLogic EJB forum:
    WebLogic Server - EJB

  • Concurrent managers problem 11.5.9

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

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

  • Concurrent managers ( JVM)

    I have a R12 Vision environment installed on Solaris 5.10 on 2 nodes, with batch processing ( and database) on one node ( Node A), and rest of the apps tier services running on the second node ( Node B).
    What I wanted to find out was the memory requirement for this environment. The purpose is to use this to get a better idea of the hardware requirement for 10 instances of Oracle Applications which we need to create as part of a fresh implementation.
    So, I thought, I'll check the default sizes needed for running
    a) database
    b) applications
    a) database part I've taken care of
    b) applications:
    On node B ( web / forms tier)
    First I wanted to check the default sizes of all the JVMs installed.
    I understand that on the 3 of the JVMs start up with the following default max heap size
    FORMS JVM
    -Xmx256M
    OACORE JVM
    -Xmx512M
    OAFM JVM
    -Xmx256M
    On Node A ( concurrent processing )
    When I do a
    ps -ef |grep applmgr |grep -i DCLIENT
    I see some 12 processes for these
    applmgr 3701 3637 0 Sep 10 ? 7:52 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
    applmgr 3703 3637 0 Sep 10 ? 8:23 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
    applmgr 3695 3637 0 Sep 10 ? 17:28 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
    applmgr 3699 3637 0 Sep 10 ? 8:17 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
    applmgr 3694 3637 0 Sep 10 ? 8:21 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
    applmgr 3697 3637 0 Sep 10 ? 16:05 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
    applmgr 3696 3637 0 Sep 10 ? 16:43 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
    applmgr 3700 3637 0 Sep 10 ? 8:17 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
    applmgr 3698 3637 0 Sep 10 ? 7:46 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
    applmgr 3704 3637 0 Sep 10 ? 10:06 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
    applmgr 3705 3637 0 Sep 10 ? 8:14 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
    applmgr 3706 3637 0 Sep 10 ? 8:18 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
    All of these have the parent process id as 3637, which is the process for the service manager ( FNDSM)
    ptre 3637
    3637 FNDSM
    3673 RCVOLTM APPS/ZGA5A000CCA376B92E66589EB9B640008522DC5AB54ED497EBE6F1E7A2ED33AB28
    3674 RCVOLTM APPS/ZG72B4C04ED1376DF24AEB2C215881578D8D686F4949F8BBDF82CACEC6CAA4C430
    3675 POXCON APPS/ZGBEBFD251987E7FDC7DAE7D07CBEAE239F56E3DEB751B28748B9B3054CA3BFFAD3
    3676 CYQLIB APPS/ZG779BC67A13CBACE567402671E31D0E0282FD0041A8E62272F6A82484551509A09
    3677 INCTM APPS/ZGC797A91F15553AC4DC6E7789E860FED9F169749E2D2105716F18C876041CF17AEF
    3694 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
    3695 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
    3696 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
    3697 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
    3698 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
    3699 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=36
    3700 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
    3701 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
    3702 /u03/oracle/VIS/apps/apps_st/appl/xdp/12.0.0/bin/XDPCTRLS APPS/ZG0D1E37E24F57F5
    3703 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
    3704 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
    3705 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
    3706 /u03/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin/java -DCLIENT_PROCESSID=37
    3709 FNDCRM APPS/ZGC0523DAB50578CE9E103ACBB0BCABC57132ECA88FB1B92855FCFFDACE64E9CEF9
    3710 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG58C402AF965363D362B15E3D
    3711 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG3A071441461117B4AB0C1148
    3712 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZGCAC037E40629DC25B6A64439
    3713 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG7C22F67D5B10AE3786CF3C58
    3714 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG7C22F67D5B10AE3786CF3C58
    3715 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG7C22F67D5B10AE3786CF3C58
    3716 PALIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG56731173E63F582D799ECCE8F
    3717 INVLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG5897C948C8DFB32F39009E03
    3719 MRCLIB FND Concurrent_Processor MANAGE OLOGIN="APPS/ZG0004527A8F95E64C57A399EA0
    What I'm trying to understand is are these many JVMs being spawned by concurrent managers?
    If yes, where exactly do I look for to see their JVM sizes?
    When I do a top and check the memory of these java processes, each of them seem to be using 211M each ( approx). I would want some control on this. Possibly shutdown the managers which are not needed.
    If anyone can throw some light on this concurrent managers and JVMs relationship, it'll be much helpul.

    Pretty much every Concurrent Manager known to man is started out of the box in R12. You have to decide what Concurrent Managers can be safely disabled based on what products/modules are in use. You only have to have Internal Manager, Conflict Resolution Manager, Service Managers and Standard Manager. Deactivating the SFM% managers and Workflow Managers will save a ton java resources. Workflow will require the Workflow Agent Listeners to be up. You can stop the Workflow Service Components in Oracle Applications Manager for products you are not using (ECX% for example). These will each spawn a seperate java process.

  • Managers not coming up

    I am having trouble with my managers in release 12.1.1. I am running a fresh install.
    After running adcmctl.sh start the internal manager 'seems' to stay up for a few seconds (I see it coming up in the sysadmin --> concurrent --> manager --> administer) but crashes without actually starting any processes or requests (there are none in queue anymore btw).
    I read the following error(s) in the manager's log:
    ========================================================================
    Starting VIS_0812@VIS Internal Concurrent Manager -- shell process ID 26535
    logfile=/d01/oracle/VIS/inst/apps/VIS_ebsinstance/logs/appl/conc/log/VIS_0812.mgr
    PRINTER=noprint
    mailto=applmgr
    restart=N
    diag=N
    sleep=30
    pmon=4
    quesiz=1
    Reviver is ENABLED
    expr: syntax error
    The Internal Concurrent Manager has encountered an error.
    Review concurrent manager log file for more detailed information. : 12-AUG-2010 00:45:54 -
    Shutting down Internal Concurrent Manager : 12-AUG-2010 00:45:55
    List of errors encountered:
    _ 1 _
    Error in DBMS lock request by handle. (ROUTINE=AFPGMG) (REASON=afpdlrh
    received an unsuccessful result from PL/SQL procedure or function
    FND_DCP.Check_Process_Status_By_Handle.
    Routine FND_DCP.CHECK_PROCESS_STATUS_BY_HANDLE received a result code
    of 5 fr
    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.
    expr: syntax error
    sh: mail: not found
    The VIS_0812@VIS internal concurrent manager has terminated with status 1 - giving up.
    Does anyone have an idea what's going on here?
    Running CMCLEAN.sql gives the following error:
    SQL> @/mnt/hgfs/shared/cmclean.sql
    DOC>
    DOC> WARNING : Do not run this script without explicit instructions
    DOC>          from Oracle Support
    DOC>
    DOC>
    DOC> *** Make sure that the managers are shut down     ***
    DOC> *** before running this script               ***
    DOC>
    DOC> *** If the concurrent managers are NOT shut down, ***
    DOC> *** exit this script now !!               ***
    DOC>
    DOC>#
    If you wish to continue type the word 'dual': dual
    -- Updating invalid process status codes in FND_CONCURRENT_PROCESSES
    Manager short name Process id Status code
    FNDICM               2028098 A
    FNDCRM               2028111 A
    RCVOLTM14          2028102 A
    RCVOLTM           2028101 A
    OAMCOLMGR          2028115 A
    WFALSNRSVC          2028110 A
    WFMLRSVC          2028109 A
    WFWSSVC           2028108 A
    FNDCPOPP          2028107 A
    DownloadProcessorNor     2028106 A
    malMode
    FFTM               2028100 A
    UPDATE     fnd_concurrent_processes
    ERROR at line 1:
    ORA-00600: internal error code, arguments: [13013], [5001], [3259613],
    [855663735], [13], [855663735], [17], [], [], [], [], []
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    I have searched google and the OTN forums for days now but can't find the answer to any of these errors. Who can help?

    'd oh...... a typo indeed, but in my sql statement. I'm deeply ashamed. The right output should be:
    SQL> select owner, object_name, status
    2 from dba_objects
    3 where object_name = 'FND_CONCURRENT_PROCESSES';
    OWNER
    OBJECT_NAME
    STATUS
    APPLSYS
    FND_CONCURRENT_PROCESSES
    VALID
    APPS
    FND_CONCURRENT_PROCESSES
    VALID
    OWNER
    OBJECT_NAME
    STATUS
    still looking for the logfile. Will get back to that later.
    Update:
    Logfile found. Rebooted my db and the logfile shows:
    DB Logfile:Fri Aug 13 01:47:23 2010Stopping background process SMCO
    Stopping background process FBDA
    Shutting down instance: further logons disabled
    Fri Aug 13 01:47:26 2010
    Stopping background process CJQ0
    Stopping background process QMNC
    Stopping background process MMNL
    Stopping background process MMON
    Shutting down instance (immediate)
    License high water mark = 3
    ALTER DATABASE CLOSE NORMAL
    Fri Aug 13 01:47:33 2010
    SMON: disabling tx recovery
    SMON: disabling cache recovery
    Fri Aug 13 01:47:40 2010
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Thread 1 closed at log sequence 14
    Successful close of redo thread 1
    Fri Aug 13 01:47:56 2010
    Completed: ALTER DATABASE CLOSE NORMAL
    ALTER DATABASE DISMOUNT
    Completed: ALTER DATABASE DISMOUNT
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Fri Aug 13 01:48:00 2010
    Stopping background process VKTM:
    Fri Aug 13 01:48:13 2010
    Instance shutdown complete
    Fri Aug 13 01:50:00 2010
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Fri Aug 13 01:50:14 2010
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_1 parameter default value as /d01/oracle/VIS/db/tech_st/11.1.0/dbs/arch
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =44
    Fri Aug 13 01:50:27 2010
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 11.1.0.7.0.
    Using parameter settings in client-side pfile /d01/oracle/VIS/db/tech_st/11.1.0/dbs/initVIS.ora on machine ebsinstance
    System parameters with non-default values:
    processes = 200
    sessions = 400
    timed_statistics = TRUE
    shared_pool_size = 400M
    shared_pool_reserved_size= 40M
    nls_language = "american"
    nls_territory = "america"
    nls_sort = "binary"
    nls_date_format = "DD-MON-RR"
    nls_numeric_characters = ".,"
    nls_comp = "binary"
    nls_length_semantics = "BYTE"
    sga_target = 1G
    control_files = "/d01/oracle/VIS/db/apps_st/data/cntrl01.dbf"
    control_files = "/d01/oracle/VIS/db/apps_st/data/cntrl02.dbf"
    control_files = "/d01/oracle/VIS/db/apps_st/data/cntrl03.dbf"
    db_block_checksum = "TRUE"
    db_block_size = 8192
    compatible = "11.1.0"
    log_buffer = 10485760
    log_checkpoint_interval = 100000
    log_checkpoint_timeout = 1200
    db_files = 512
    log_checkpoints_to_alert = TRUE
    dml_locks = 10000
    undo_management = "AUTO"
    undo_tablespace = "UNDO_TBS"
    db_block_checking = "FALSE"
    sec_case_sensitive_logon = FALSE
    session_cached_cursors = 500
    utl_file_dir = "/usr/tmp"
    utl_file_dir = "/usr/tmp"
    utl_file_dir = "/d01/oracle/VIS/db/tech_st/11.1.0/appsutil/outbound/VIS_ebsinstance"
    utl_file_dir = "/usr/tmp"
    plsql_native_library_dir = "/d01/oracle/VIS/db/tech_st/11.1.0/plsql/nativelib"
    plsql_native_library_subdir_count= 149
    plsql_code_type = "INTERPRETED"
    plsql_optimize_level = 2
    job_queue_processes = 2
    systemtrig_enabled = TRUE
    cursor_sharing = "EXACT"
    parallel_min_servers = 0
    parallel_max_servers = 8
    db_name = "VIS"
    open_cursors = 600
    ifile = "/d01/oracle/VIS/db/tech_st/11.1.0/dbs/VIS_ebsinstance_ifile.ora"
    sortelimination_cost_ratio= 5
    btree_bitmap_plans = FALSE
    fastfull_scan_enabled = FALSE
    query_rewrite_enabled = "true"
    indexjoin_enabled = FALSE
    sqlexecprogression_cost= 2147483647
    likewith_bind_as_equality= TRUE
    pga_aggregate_target = 1G
    workarea_size_policy = "AUTO"
    optimizerautostats_job = FALSE
    optimizer_secure_view_merging= FALSE
    aq_tm_processes = 1
    olap_page_pool_size = 4M
    diagnostic_dest = "/d01/oracle/VIS/db/tech_st/11.1.0/admin/VIS_ebsinstance"
    tracefiles_public = TRUE
    max_dump_file_size = "20480"
    Fri Aug 13 01:50:33 2010
    WARNING:Oracle instance running on a system with low open file descriptor
    limit. Tune your system to increase this limit to avoid
    severe performance degradation. Current limit = 992
    PMON started with pid=2, OS id=3450
    Fri Aug 13 01:50:34 2010
    VKTM started with pid=3, OS id=3452
    VKTM running at (100ms) precision
    Fri Aug 13 01:50:35 2010
    DIAG started with pid=4, OS id=3458
    Fri Aug 13 01:50:35 2010
    DBRM started with pid=5, OS id=3462
    Fri Aug 13 01:50:35 2010
    PSP0 started with pid=6, OS id=3464
    Fri Aug 13 01:50:35 2010
    DIA0 started with pid=7, OS id=3466
    Fri Aug 13 01:50:36 2010
    MMAN started with pid=8, OS id=3468
    Fri Aug 13 01:50:37 2010
    DBW0 started with pid=9, OS id=3470
    Fri Aug 13 01:50:38 2010
    LGWR started with pid=10, OS id=3472
    Fri Aug 13 01:50:38 2010
    CKPT started with pid=11, OS id=3474
    Fri Aug 13 01:50:38 2010
    SMON started with pid=12, OS id=3476
    Fri Aug 13 01:50:38 2010
    RECO started with pid=13, OS id=3479
    Fri Aug 13 01:50:39 2010
    MMON started with pid=14, OS id=3481
    Fri Aug 13 01:50:39 2010
    MMNL started with pid=15, OS id=3483
    Fri Aug 13 01:50:39 2010
    ORACLE_BASE not set in environment. It is recommended
    that ORACLE_BASE be set in the environment
    Fri Aug 13 01:50:40 2010
    ALTER DATABASE MOUNT
    Setting recovery target incarnation to 2
    Successful mount of redo thread 1, with mount id 280699184
    Database mounted in Exclusive Mode
    Lost write protection disabled
    Completed: ALTER DATABASE MOUNT
    Fri Aug 13 01:50:45 2010
    ALTER DATABASE OPEN
    Fri Aug 13 01:50:50 2010
    Thread 1 opened at log sequence 14
    Current log# 2 seq# 14 mem# 0: /d01/oracle/VIS/db/apps_st/data/log2.dbf
    Successful open of redo thread 1
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Fri Aug 13 01:50:50 2010
    SMON: enabling cache recovery
    Fri Aug 13 01:50:53 2010
    Incremental checkpoint up to RBA [0xe.76b5.0], current log tail at RBA [0xe.76b5.0]
    Fri Aug 13 01:51:01 2010
    Successfully onlined Undo Tablespace 18.
    Verifying file header compatibility for 11g tablespace encryption..
    Verifying 11g file header compatibility for tablespace encryption completed
    Fri Aug 13 01:51:01 2010
    SMON: enabling tx recovery
    Database Characterset is AL32UTF8
    Opening with internal Resource Manager plan
    Fri Aug 13 01:51:24 2010
    Starting background process FBDA
    Fri Aug 13 01:51:24 2010
    FBDA started with pid=17, OS id=3498
    Fri Aug 13 01:52:14 2010
    replication_dependency_tracking turned off (no async multimaster replication found)
    Fri Aug 13 01:52:42 2010
    Starting background process QMNC
    Fri Aug 13 01:52:42 2010
    QMNC started with pid=18, OS id=3511
    Fri Aug 13 01:59:23 2010
    Completed: ALTER DATABASE OPEN
    >
    so, no ORA-00600 errors there.
    Edited by: Snowgasm on 13-aug-2010 10:51
    >SQL> @cmclean.sql
    DOC>
    DOC> WARNING : Do not run this script without explicit instructions
    DOC>          from Oracle Support
    DOC>
    DOC>
    DOC> *** Make sure that the managers are shut down     ***
    DOC> *** before running this script               ***
    DOC>
    DOC> *** If the concurrent managers are NOT shut down, ***
    DOC> *** exit this script now !!               ***
    DOC>
    DOC>#
    If you wish to continue type the word 'dual': dual
    -- Updating invalid process status codes in FND_CONCURRENT_PROCESSES
    Manager short name Process id Status code
    FNDICM               2028098 A
    FNDCRM               2028111 A
    RCVOLTM14          2028102 A
    RCVOLTM           2028101 A
    OAMCOLMGR          2028115 A
    WFALSNRSVC          2028110 A
    WFMLRSVC          2028109 A
    DownloadProcessorNor     2028106 A
    malMode
    FFTM               2028100 A
    WFWSSVC           2028108 A
    FNDCPOPP          2028107 A
    UPDATE     fnd_concurrent_processes
    ERROR at line 1:
    ORA-00600: internal error code, arguments: [13013], [5001], [3259613],
    [855663735], [13], [855663735], [17], [], [], [], [], []
    >
    Now when I check the logfile for the DB again I see the following entry added:
    >Fri Aug 13 02:01:38 2010
    Starting background process SMCO
    Fri Aug 13 02:01:38 2010
    SMCO started with pid=16, OS id=3587
    Fri Aug 13 02:02:20 2010
    Starting background process CJQ0
    Fri Aug 13 02:02:20 2010
    CJQ0 started with pid=24, OS id=3599
    Fri Aug 13 02:04:11 2010
    Errors in file /d01/oracle/VIS/db/tech_st/11.1.0/admin/VIS_ebsinstance/diag/rdbms/vis/VIS/trace/VIS_ora_3617.trc (incident=12997):
    ORA-00600: internal error code, arguments: [13013], [5001], [3259613], [855663735], [13], [855663735], [17], [], [], [], [], []
    Incident details in: /d01/oracle/VIS/db/tech_st/11.1.0/admin/VIS_ebsinstance/diag/rdbms/vis/VIS/incident/incdir_12997/VIS_ora_3617_i12997.trc
    Fri Aug 13 02:05:00 2010
    Trace dumping is performing id=[cdmp_20100813020500]
    Fri Aug 13 02:05:03 2010
    Sweep Incident[12997]: completed
    >
    Edited by: Snowgasm on 13-aug-2010 11:06
    Edited by: Snowgasm on 13-aug-2010 11:09

  • Two node installation with 2 concurrent managers..

    Need your help. I have 12.1.1 Two node installation on Linux 5.9 with 64 bit.
    Linux2- Database server + Concurrent manager
    Linux1- Apps Node
    Port - 8002 (port pool -2)
    on my app node - linux1, I have 2 directories <SID>_linux1 and <SID>_linux2. First one is for primary apps node and second one is for 2nd concurrent manager. It is a shared directory structure. I have 2 questions:
    1) If I run the autoconfig on Linux1, I can run all the services and connect to apache. However, If I run the autconfig on linux2, I will not be able to connect to web server (for a short time request will be sent to Linux1 and then it gets forwarded to Linux2 - even though Linux2 is not app server).
    2) How do I run the second concurrent manager on LInux2? After I run the 2 concurrent manager, how do I test both concurrent managers are working?
    Your help is much appreciated.

    Hi Hussein,
    Thank you for the info. I was wondering whether the Linux2 concurrent manager was installed correctly or not. I went to xml file and found these entries and it made me think, it didn't install correctly because only concurrent manager should have been yes and the rest should be no. Isn't it? If it is wrong, how do I correct this?
    <oa_system_config>
             <TIER_DB oa_var="s_isDB">NO</TIER_DB>
             <TIER_ADMIN oa_var="s_isAdmin">YES</TIER_ADMIN>
             <TIER_WEB oa_var="s_isWeb">YES</TIER_WEB>
             <TIER_FORMS oa_var="s_isForms">YES</TIER_FORMS>
             <TIER_NODE oa_var="s_isConc">YES</TIER_NODE>
             <TIER_FORMSDEV oa_var="s_isFormsDev">YES</TIER_FORMSDEV>
             <TIER_NODEDEV oa_var="s_isConcDev">YES</TIER_NODEDEV>
             <TIER_WEBDEV oa_var="s_isWebDev">YES</TIER_WEBDEV>
             <config_option type="techstack" oa_var="s_techstack">as1013</config_option>
             <config_option type="techstack" oa_var="s_tnsmode">generateTNS</config_option>
             <config_option type="adx" oa_var="s_apps_version">12.1.1</config_option>
             <config_option type="techstack" oa_var="s_apache_mode">NORMAL</config_option>
             <ias_version oa_var="s_ias_version">10.1.3.4.0</ias_version>
          </oa_system_config>

  • Target node/queue unavailable for 12i Concurrent Managers on Redhat Linux

    Hi,
    I was able to sucessfully install Release 12 Vision on Redhat Linux.. Every thing is working fine but concurrent managers are not active except the Internal Manager. Rest of the Managers has no value in the node name field and the status is "Target node/queue unavailable".. I also ran adcmcmtl.sh to manually stop and start the managers but still facing the same issue..
    Please tell me what i'm missing..
    Thanks in Advance,
    Prasad

    Duplicate post ..
    Re: Not able to start the concurrent Managers in Release 12 on Redhat Linux 4
    I suggest we follow up on one post so we can get more input from others.

  • Concurrent Manger not startted after clone in apps 11i

    Hi All,
    After clone refresh concurrent managers are not started. The value of concurrent_queue_name, node_name is not correct in table fnd_concurrent_queues table.
    O/P of the queries
    SQL> SELECT trigger_name , status FROM user_triggers WHERE table_name = 'FND_NODES' ;
    TRIGGER_NAME STATUS
    UPNAME ENABLED
    FNDSM ENABLED
    SQL> select concurrent_queue_name, node_name from fnd_concurrent_queues where manager_type=6;
    CONCURRENT_QUEUE_NAME NODE_NAME
    FNDSM_CLONEAPPL CLONEAPPL
    FNDSM_PRODDB PRODDB
    FNDSM_PRODAPPL PRODAPPL
    FNDSM_AUTHENTICATION AUTHENTICATION
    It would contain value as clonedb instead of proddb. can i manually edit this table and retest the issue?
    Please any suggestions will be greatly appreciated.
    Thanks in Advance.

    Hi,
    Can you find any errors in the CM log file?
    Please follow the steps in (Note: 391406.1 -      How to get a clean Autoconfig Environment) to clean FND_NODES table and run AutoConfig on the database and the application tier nodes, and check then. You may also run cmclean.sql (Note: 134007.1 )once AutoConfig is done and before starting the CM.
    Regards,
    Hussein

  • Help regarding Inventory related concurrent managers to be assigned

    Hi,
    I am looking for a help regarding the below aspects
    1)Which concurrent managers needs to be assigned to run the following five concurrent programs.
    INV Transaction Worke
    Inventory transaction worker
    Interface Trip Stop
    Min Max report planning
    Pick selection List Generation
    2)We are facing issues with the above jobs. Currently except Inventory transaction worker all the other concurrent programs are running under standard manager.
    because of which Min max planning report programs are piling up under standard manager. Min max programs were going to “Pending” status and never getting picked up as they were waiting for other programs in the queue to get finished. There were thousands piled up after the environment was bring up.
    How can we solve this issue.. please suggest

    835129 wrote:
    The metalink notes you provided didnt gave me any information about the concurrent managers under which these programs should run. Any help regarding concurrent managers would be helpfulI believe you have not read my reply properly since I mentioned "WIP Move Manager and Inventory Manager". Plus, the docs mention it clearly so please read it again!
    Thanks,
    Hussein

Maybe you are looking for