Concurrent managers down

Dear All,
Today morning concurrent managers were down on production. when i checked the concurrent logs observed the following error.
Shutting down Concurrent Manager : 27-FEB-2012 04:21:24
List of errors encountered:
_ 1 _
Routine AFPSMG encountered an ORACLE error. ORA-00604: error occurred
at recursive SQL level 2
ORA-04031: unable t.
Review your error messages for the cause of the error. (=<POINTER>)
_ 2 _
Routine AFPGSR encountered an ORACLE error. ORA-04031: unable to
allocate 16 bytes of shared memory ("shared pool".
Review your error messages for the cause of the error. (=<POINTER>)
then we restarted the cocurrent managers and they are working fine.
I just want to know the cause of this error.
Thanks.

Hi
The error :ORA-04031: unable to allocate 16 bytes of shared memory.
indicates that there is not enough sufficient memory in the shared pool for the processes
You need to check the alert log file of the database to see if there are similar error messages and then do Flush shared pool. This should take care of the issue if it has come once.
ALTER SYSTEM FLUSH SHARED_POOL;
If this does not work:
Increase the shared memory or a simple DB bounce could resolve the issue.
Regards
Shalini

Similar Messages

All Concurrent managers going down (Except Internal conc manager)

Hi All,
We are on Oracle Apps R12.0.4 and Db 10g
We have done a cloning from RAC ASM 2 node instance to Non-RAC NonASM single node.
The problem is that concurrent managers (Standard manager and other manangers) are going down automatically.
ICm obviously is trying to bring them back .
here is the log file:
Starting INVMGR Concurrent Manager : 29-JUN-2010 07:49:18
Process monitor session ended : 29-JUN-2010 07:49:18
Process monitor session started : 29-JUN-2010 07:51:18
Adding Node:(APP2), to unavailable list
Found dead process: spid=(28003), cpid=(240974), ORA pid=(44), manager=(0/4)
Found dead process: spid=(28002), cpid=(240973), ORA pid=(43), manager=(0/5)
Starting FNDSCH Concurrent Manager : 29-JUN-2010 07:51:18
Starting FNDCRM Concurrent Manager : 29-JUN-2010 07:51:18
Starting OAMCOLMGR Concurrent Manager : 29-JUN-2010 07:51:18
Starting FTE_TXN_MANAGER Concurrent Manager : 29-JUN-2010 07:51:18
Starting IEU_SH_CS Concurrent Manager : 29-JUN-2010 07:51:18
Starting IEU_WL_CS Concurrent Manager : 29-JUN-2010 07:51:18
Starting PASMGR Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting STANDARD Concurrent Manager : 29-JUN-2010 07:51:18
Starting INVMGR Concurrent Manager : 29-JUN-2010 07:51:18
Process monitor session ended : 29-JUN-2010 07:51:18
+++++++++++++++++++++++++++++++++++++++++
What i wanted to know is "Adding Node:(APP2), to unavailable list"
What does this mean and how to troubleshoot it ?
Also, i can see that STATUS column in FND_NODE table is set to "N"
Does it mean something which affects the concurrent managers?
Please help me resolve this.
Thanks,
KK

Hi,
The problem is that concurrent managers (Standard manager and other manangers) are going down automatically.
ICm obviously is trying to bring them back .Please verify the definition of the CMs and make sure none points to the RAC instances.
I would suggest you stop the CM, purge FND_NODES table and run AutoConfig on the database/application tier nodes, run cmclean.sql script, then start the CM and see if you can reproduce the issue.
Thanks,
Hussein

Shut down the concurrent managers to terminate the process ORA-01000

Dear All,
Error As Follows
Shut down the concurrent managers to terminate the process or use port-specific operating system commands to terminate the process.
Job number is: 638
Job number is: 639
01-FEB-2013 10:46:36 - ORACLE error 1000 in get_status
The SQL statement being executed at the time of the error was: &SQLSTMT and wJob number is: 642
The call to function PingProcess in cartridge AQCART has failed.
Routine FNDSM cannot terminate the concurrent process with concurrent process ID &CPID and
operating system process ID 7537140
The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
01-FEB-2013 10:44:34 - ORACLE error 1000 in get_status
Cause: get_status failed due to ORA-01000: maximum open cursors exceeded.
Again after some time i used to get this error
Cause: get_status failed due to ORA-01000: maximum open cursors exceeded.
The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
01-FEB-2013 11:12:15 - ORACLE error 1000 in get_status
Cause: get_status failed due to ORA-01000: maximum open cursors exceeded.
The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
The call to function PingProcess in cartridge AQCART has failed.
Job number is: 651
Suggestions are welcome
Regards
Surinder Singh
Edited by: Surinder Singh on Feb 1, 2013 11:16 AM

Surinder Singh wrote:
Database Version - Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
Application Version - 11.5.10.2
Current Open cursors value
SUM(A.VALUE) NAME
28396 opened cursors current
Regards
Surinder SinghThis value is high.
Please run AutoConfig and make sure it completes successfully.
Can you find any errors in the database log file?
Thanks,
Hussein

What is the function of the Service Manager, in Concurrent Managers?

Greetings to All,
When looking at the concurrent managers, our internal manager is down and we also have the Service Manager being down. I understand the process of the Internal Manager.
But like to know what the Service Manager does and what it is used for.
Thanks in advance for any helpful information.

Hi,
Please refer to the following documents.
Note: 210062.1 - Generic Service Management (GSM) in Oracle Applications 11i
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=210062.1
Oracle® Applications System Administrator’s Guide Maintenance/Configuration manuals
http://www.oracle.com/technology/documentation/applications.html
Regards,
Hussein

Problem with Concurrent managers in RAC environment

We have 12.1.2 EBS with 2-Node RAC
Issue is that concurrent managers needs to be restarted, incase if one of the database is down. ?
But ebs fwk pages, forms all works fine, even if one of the database node is down, but CM needs a restart
Can someone let me know what could be the problem

Please see the following docs.
Parallel Concurrent Processing (PCP) Running Request Behavior when Standard Manager Failed Over [ID 1476803.1]
Concurrent Manager Functionality Not Working And PCP Failover Takes Long Inspite of Enabling DCD With Database Server [ID 438921.1
EBS - Technology Area - Webcast Recording 'E-Business Suite - RAC & Parallel Concurrent Processing (PCP)' [video] [ID 1359612.1]
Thanks,
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%

Acutal and Target Processes for two concurrent managers refuse to be equal

Hi
I have bounced the concurrent manager. I have stopped all services on the apps node then started them again.
All Actual / Target processes are now equal except two -
the OAM Generic Collection and the Output Post Processor
What, if anything, can I do for this? As they satnd, Concurrent Manger is down, still.
Thanks
EBS 11.5.10
AIX 5.2
Oracle 9.2.0.8

Someone here tells me that it isn't a good idea to worry about the iniquity of the Actual and Targer processes, if the particular manager is not one that we need, or use.
I dont know if this is correct or not.
He also tells me that checking the Dashboard to see if the CCM is up is not recommended - he explains that he only visits the Administer Concurrent Managers screen, and its there and only there that he compares the Actual to the Target.
I am not sure if he is right, but at least this question is now partly answered.
Also, I just read that "sometimes the actual process may be less than the target process due to manager deactivation" .
Thanks.
Edited by: Dan A on Dec 10, 2008 10:37 AM

Starting Concurrent Managers Fails in E-Business 12.1.3

Has anyone seen this error, all of a sudden when attempting to start the concurrent managers the following errors appear. Relinking, changing the password, cmclean, alll have been tried but to no avail. This is Linux 5.8 - 64-bit, Oracle database 10.1.0.5 EE:
Shutting down Internal Concurrent Manager : 04-OCT-2012 09:22:54
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>)
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 uat_1004@uat internal concurrent manager has terminated with status 1 - giving up.

Application Release: 12.1.3, Database Version: 11.2.0.3 (64-Bit) and OS: Linux 5.8. The password was successfully changed via FNDCPASS and all the executables were also relinked. Verified that connection can take place as the apps user and the applsys user using the new password.
Log File:
========================================================================
Starting uat_1004@uat Internal Concurrent Manager -- shell process ID 17522
logfile=/u01/app/uat/inst/apps/uat_kfc51a/logs/appl/conc/log/uat_1004.mgr
PRINTER=noprint
mailto=applprod
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. : 04-OCT-2012 03:53:12 -
Shutting down Internal Concurrent Manager : 04-OCT-2012 03:53:12
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>)
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 uat_1004@uat internal concurrent manager has terminated with status 1 - giving up.

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

After Cloning Concurrent managers erroring out while coming up

Hi
I have cloned the r12.1.1 instance all the things are successful but the concurrent managers are not coming up.
I checked the by login as sysadmin concurrent-->administer-->select standard manager-->processes log file i found the following errors
Application Object Library: Concurrent Processing version 11.5
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
STANDARD Concurrent Manager started : 05-OCT-2011 13:33:49
05-OCT-2011 13:33:49
Starting concurrent program FNDWFBG for concurrent request 19347388 (MODULE=FNDWFBG)
05-OCT-2011 13:33:50
Starting concurrent program FNDWFBG for concurrent request 19347390 (MODULE=FNDWFBG)
Routine AFPCSQ encountered an ORACLE error. ORA-12170: TNS:Connect timeout occurred
Review your error messages for the cause of the error. (=<POINTER>)
Shutting down Concurrent Manager : 05-OCT-2011 13:37:04
ORA-01012: not logged on
ORACLE error 3114 in AFPRSR-Resubmit_Time
Cause: AFPRSR-Resubmit_Time failed due to ORA-03114: not connected to ORACLE
The SQL statement being executed at the time of the error was: and was executed from the file .
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 AFPPRD has encountered a fatal error. ORA-03114: not connected
to ORACLE
Contact your system administrator or support representative.
_ 3 _
Routine AFPCSQ encountered an ORACLE error. ORA-12170: TNS:Connect
timeout occurred
Review your error messages for the cause of the error. (=<POINTER>)
I tried to trouble shoot the issue by doing the following things
1)stop all Appl services
2)stop database and listener
3)start db and listener
4)as a apps user
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
5)run Auotconfig on DB Tier
6)as a apps user execute the following script
SQL> @$FND_TOP/patch/115/sqlafdcm037.sql;
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like 'FNDSM%';
7)ran adrelink for FND module
Go to cd $FND_TOP/bin
$ adrelink.sh force=y "fnd FNDLIBR"
$ adrelink.sh force=y "fnd FNDSM"
$ adrelink.sh force=y "fnd FNDFS"
$ adrelink.sh force=y "fnd FNDCRM"
8)run autoconfig on appl tier
9)run cmclean.sql
10) start all the application services.
All went fine but the concurrent manager are terminating with the error messages above....
Please can any one help on this....
Thanks
SAI

Hi,
I think it is the issue with standard manager. during startup of application triger to intialize standard manager service is not working fine.
Execute the following to alter trigger FNDSM:
CREATE OR REPLACE TRIGGER fndsm
AFTER INSERT OR UPDATE ON FND_NODES
FOR EACH ROW
BEGIN
if ( :new.NODE_NAME <> 'AUTHENTICATION' ) then
if ( (:new.SUPPORT_CP='Y')
or (:new.SUPPORT_FORMS='Y')
or (:new.SUPPORT_WEB='Y') ) then
fnd_cp_fndsm.register_fndsm_fcq(:new.NODE_NAME);
end if;
if (:new.SUPPORT_CP = 'Y') then
fnd_cp_fndsm.register_fndim_fcq(:new.NODE_NAME);
end if;
end if;
END;
commit;
Clean FND_NODES by executing the following:
exec FND_CONC_CLONE.SETUP_CLEAN;
Run autoconfig.
Restart concurrent managers and retest.
Hope this may help...!!!
Regards RanjanS

Erratic behaviour of Concurrent Managers

We have PCP configured on 2 node EBS. We have recently started seeing that our FNDSM on node 2 stops working and also couple of other managers got deativated. When we try to start them manually they won't start. The only thing we do is to bounce application services as pointed out in "Note ID 245563.1 Concurrent Processing - The Concurrent Manager Fails to Start on GSM Enabled Due to DBMS_LOCK.Request ResultCall Failed to Establish ICM" which is not always possible in production:
ICM log file showed:
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.
I went through the note: Concurrent Managers Will Only Start on One Node in PCP/RAC Environment (Doc ID 264296.1)
So I have questions regarding this:
1. Does ICM runs only on primary node as I believe?
2. When starting the application we start the node 1 and then node 2 by using adstartal.sh which internally executes adcmctl.sh on both the nodes, as the note points out we should run adcmctl.sh only from primary node. How to solve this problem?
3. If this issue is common how should we start application on another node and still not execute adcmctl.sh?

1. Does ICM runs only on primary node as I believe?You can setup the internal manager on both nodes but it will start (be running) on one node only.
How to Setup and Test Failover of PCP on Non-RAC Environments. [ID 743716.1]
Can a Concurrent Manager Tier be Added Without Setting Up PCP? [ID 389876.1]
2. When starting the application we start the node 1 and then node 2 by using adstartal.sh which internally executes adcmctl.sh on both the nodes, as the note points out we should run adcmctl.sh only from primary node. How to solve this problem?You can start adcmctl.sh on both nodes so you use adstrtal.sh on both nodes and the internal manager will be running on one node only.
3. If this issue is common how should we start application on another node and still not execute adcmctl.sh?I have already answered this above.
Thanks,
Hussein

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.

How to assign particular concurrent requests to sparate concurrent managers

How to assign particular Users concurrent requests to custom or Sparate concurrent managers
OS : Linux
Apps: 11.5.10.2

Hi,
This can be done via "Specialization Rules".
How to Create a Custom Concurrent Manager [ID 170524.1
How to Split the Load of Work to Many Concurent Managers [ID 473310.1]
Oracle Applications System Administrator's Guide - Configuration (zipped) -- Page 7-14
http://download.oracle.com/docs/cd/B25516_18/current/acrobat/115sacg.zip
Make sure you bounce the CM once you are done.
Thanks,
Hussein

V$license and concurrent managers

Are concurrent managers considered part of session limits in terms of licensing. In other words, do they count as sessions towards license limits?
Thanks.

Hi,
Please find these docs
Concurrent Managers Fail To Start After New Install of Release 12 (Doc ID 413164.1)
ICM Not Starting: Node Name not Registered (Doc ID 602942.1)
Regards
Yoonas

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 down

Similar Messages

Maybe you are looking for