Widows XP - Concurrent Manager - Target node/queue unavailable!

Dear All,
Need help to run concurrent Manager, all services are up, started, but all request are inactive, no manager, I tried my best to solve this problem thru metalink, updating FND......, its activating and suddenly status changing to target node/queue unavailable.
Please give me some idea how to sort this problem, when intalling 11i there is some error came memory error and i cancelled, then it proceeded and completed installation.
Regards,
Williams.

Hi All,
I am also facing same problem and did you got the any soluation.
I am getting below problem, while trying to install E-Business suite on Windows server XP,
RW-50011 :ERROR:- Operating system patch/version test has returned an error:1
Moreover I have prox 92 GB disk space free, but it's giving errors, there is no enough free space on disk...
Warm regards
raags INDIA
[email protected]

Similar Messages

Standard Manager Target node/queue unavailable

Hello everybody!!
I am having problems with SM ( Standard manager ), I see that all my Oracle Applications is working fine, but when I deploy one request ( ex. report ) have error, the request is phase inactive and Status not manager.
The button diagnostics says
""This request will not be processed because there are currently no managers running that can process it.
This is an error condition. There are one or more managers defined that can process this request that should be running at this time, but do not appear to be running""
In the OAM try to start a Standard manager but was error Targer node / queue unavailable
SO Red hat Enterprise 4
i need help

You are posting in the wrong forum. This is for Oracle Business Intelligence Applications, not Oracle Applications 11i / EBusiness Suite.

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.

Target node/queue unavailable

Hi Friends,
Just Now I have completed my 2 node 11.5.10.2 installation on Linux......
(a) Database node on one machine ( Purely Database)
(b) Application Tier on one Machine ( Forms,web, admin and Concurrent Manager)
I have completed installation succesfully.... I did not see any errors while instalaltion....
But I am getting one problem regarding Concurrent Managers....
All Managers are showing as Target node/queue unavailable except Internal Manager .....
It is showing the Target node/queue unavailable for the following Managers
(a) Conflict Resolution Manager
(b) Scheduler/Prereleaser Manager
(c) Session History Cleanup
(d) UWQ Worklist Items Release for Crashed session
(e) Inventory Manager
(f) Standard Manager
what to do in this case...please it is urgent...

Thanks Hussein,
I understood what you are saying....
In Application Node....
in My Application context file....TNS_ADMIN is pointing to the following location
/u01/testcomn/conf/TEST_appserver/8.0.6/network/admin/TEST_appserver
Why it happened, i dont know...can we change this in context file ????
eventhough, i am not getting any problems...concurrent requests are running successfully in 2 node installation....
one more thing.....
===================================================
in my Application Node...in $COMMON_TOP
i have the conf directory..which i did not see this directory in single node installation...
this is the directory strucutre created in COMMON_TOP
/u01/testcomn/conf
/u01/testcomn/conf/TEST_appserver/
/u01/testcomn/conf/TEST_appserver/8.0.6
/u01/testconn/conf/TEST_appserver/iAS
/u01/testcomn/conf/TEST_appserver/8.0.6 directory contains the following
TEST_appserver.env TEST.env discwb4 network reports60 tools vbroker
/u01/testcomn/conf/TEST_appserver/iAS directory contains the following
Apache CAATEST_dana2.env CAATEST.env network oem_webstage soap
====================================
I have never seen the above strucuture in single node installation...but in 2 node installation..it is showing
conf directory in COMMON_TOP
==========================================
I have[b] Database on one Node and Application tier on another Node.....while multinode installation, by default Share Application Tier file system is checked in 11.5.10.2 in screens.....i think it is not required for my setup, because I have database on one node and Applications on another node. But I run the installation with checking the Sharing Application Tier File System..(Database on one node and Applications on another node)
if we want to have one of the Application Servers(Admin,CP,Forms,Web) on both the nodes, then sharing the Applications Tier is required.
With having share application tier file system in my 2 node installation will it effect my Environment...
please suggest...I am thinking that, conf directory is created because of that only......
This is my Test Server...not my production..

Target node/queue unavailable after clone

Target node/queue unavailable error after clone.
All nodes are updated (accordingly to the structure) in fnd_nodes
Please help
EBS 11.5.10.2
DB 9.2.0.8.0

Hi;
Acc to this note the cause is "FND_NODES was not populated correctly. " after a node was added. This issue is just coming after a clone and the table FND_NODES is updated properly.1. What is exact error you are hitting?
2. Did you run autoconfig on db tier than apps tier(services should be down)
If yes any error?
Regard
Helios

Concurrent Manager: Service Manager AUTHENTICATION

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

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

Error with Concurrent Manager

Hi,
I m newbie to oracle apps..Now i m facing an issue in the Councurrent Manager..The issue is
When submitting the program it being in Pending Normal state.
Diagnostics:-
The concurrent manager defined to process this request is not active in the current work shift. The request will not process within this work shift.
Contact your system administrator to verify that the concurrent manager work shifts are defined correctly.
All the Concurrent Manager Target Process having 0 value.
Internal Manger has 14 pending requests and CRM has 4 pending requests.
please advise me,
Thanks,

when i try to stop the Concurrent Manager i m getting error
adcmctl.sh stop apps/apps_passwd
Database connection could not be established. Either the database is down or the APPS credentials supplied are wrong.Are you passing the correct apps password (which is apps by default)?
Please also run cmclean.sql as per (Concurrent Processing - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]).
If you still have the same issue, please run ccml.sql script (Concurrent Processing - CCM.sql Diagnostic Script to Diagnose Common Concurrent Manager Issues [ID 171855.1]).
Thanks,
Hussein

Target/Node unavailable for Service Manager/Authtenticaion

Hi,
when ever we cloned from Production to TEST...Service Manager/Authentication Manager has Target/Node unavailable....showing this...
what might be the problem..is it normal..can we ignore it...

OK, I guess I got what you mean by "Service Manager/Authentication Manager". Please refer to:
Note: 342939.1 - Could Not Contact Service Manager FNDSM_AUTHENTICATION_PROD
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=342939.1

Concurrent Manager Node Name Issue

Hi All,
Recently one of EBS 11i (11.5.10.2 + RHEL 4.7) Node (VM Node) has been cloned to another node. So i had to change the Host name for the cloned application. I followed the meta link note 338003.1 and 341322.1. I am successfully changed the host name and able to access the application as well. When i check the Concurrent manager process's status, its showing Actual-1 and Target -1. B*ut the problem is some of process's node name is showing the previous node name (the name of the node from where cloned).* For example Output Post Processor's node name is showing the previous one and its status showing Actual - 0 and Target - 1. Please let me know why this has happened and also how can i solve this issue?
Thanks,
Mani

Please run cmclean.sql script as per (Concurrent Processing - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]) and check then.
If you still have the same issue, update FND_CONCURRENT_QUEUES table (TARGET_NODE column) -- Troubleshooting the "Error Occurred While Attempting to Establish an Applications File Server Connection" [ID 117012.1]
Please also see (Concurrent Processing - CCM.sql Diagnostic Script to Diagnose Common Concurrent Manager Issues [ID 171855.1]).
Thanks,
Hussein

Concurrent manager log CONC-SM TNS FAIL ICM failed to start for target MSOA

Hi all,
We are doing cloning from two node PCP with loadbalancer to single node application tier.
I did preclone in database and one of the node of application,
Run adcfgclone.pl in dbTier and AppsTier everything went smooth, But the Three managers are not coming up,
1. Internel manager
2.Standar manager
3.standard manager
Thease three managers are pointing to node" Prymary node of PCP
We followed the note: 555081.1 still the issue is same
The manager logfile shows:
"Check that your system has enough resources to start a concurrent manager process : 15-NOV-2008 21:20:22
Starting STANDARD Concurrent Manager : 15-NOV-2008 21:20:22
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /ebiz/u01/appltest/TEST/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.
CONC-SM TNS FAIL
Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /ebiz/u01/appltest/TEST/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.
Check that your system has enough resources to start a concurrent manager process : 15-NOV-2008 21:20:23
Starting Internal Concurrent Manager Concurrent Manager : 15-NOV-2008 21:20:23
CONC-SM TNS FAIL
: ICM failed to start for target MSOAAPPL2. Review ICM log files for additional information.
Process monitor session ended : 15-NOV-2008 21:20:23"
Please help me out in resolving this
many thanks in advance..

Hi all,
Sorted out by changing the Primary node as thhe corect node and run cmclean.sql..
Now the managers are working file..
Thanks and Regards
Vasu

Query to find concurrent programs defined in each concurrent manager queue

We have got custom concurrent queues defined and have then included applications / programs under it.
This way we are seggregating the load across multiple queues and application servers.
As a check , i want to find what programs are running / actually scheduled under each queue.
I can see the same from the application frontend. How can I find the same form backend database.
AU

Hi,
Please section "How to find out which request is handle by which concurrent queue." under the following link:
http://raghuook.blogspot.com/2010/08/apps-dba-trobleshoot-scripts.html
Also see the following link:
Checking the status of all concurent managers from backend
Requests run by a specific Concurrent Manager/Queue within the date range
Hope this helps!
Best Regards

Concurrent Manager cannot find error description for CONC-System Node

Hi friends,
I m facing a problem while doing clustering for oracle EBS.i m using hpux11i with veritas cluster server for oracle DataBase cluster.i am doing 2 node cluster.i have installed oracle 11i apps with 9i DB.thru veritas i am able to do a db cluster failover.now i want to run oracle apps 11i too from both nodes(active/passive).so i configured a virtual IP address with a Virtual Hostname which will move along with the cluster failover.when i configure ora apps tier thru giving it virtual hostname concurrent manager dies with error--Concurrent Manager cannot find error description for CONC-System Node. i tried many things but unable to come up with a solution. pls help.
regs
Satish

Please post the contents of your hosts file here.
Is FND_NODES table populated correctly? Please run AutoConfig and make sure it completes successfully.
Why are the Concurrent Managers Failing with 'CONC-System Node Name not Registered" Error After Applying Patch 6461517? [ID 1108452.1]
OPP and SFM Managers do not Start [ID 1425409.1]
Thanks,
Hussein

How OPP concurrent manager actual & target values differ?

Hi
How come OPP concurrent manager actual (6) & target (3) values differ? What causes this to change? Where as work shifts>parameter values also did not change (oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=10).
Any tip.
Regards
Arizuddin

Hi,
Please see whether the following docs applies to you:
- Number Of Output Post Processing (OPP) Processes Started Are Higher Than The Target [ID 1515086.1]
- Output Post Processor Actual Process Is 3 And Target Process Is 4 [ID 1378575.1]
And also see the following links as it is discussed before:
differnce in actual and target process-concurrent
Concurrent managers are not starting & Actual/Target count is not same
concurrent manager actual and target different
Hope this helps
Regards,

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.

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

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

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

Widows XP - Concurrent Manager - Target node/queue unavailable!

Similar Messages

Maybe you are looking for