Target node/queue unavailable or
Concurrent Manager
Solution 1 :
Take the CM bounce and check the status of managers , still you are facing the issue , you take the application full bounce and restart the CM , it will work .. I tried this it will work on my R12 Exa instance .
Solution 2 :
R12 Concurrent Managers down – Status show “Target node/queue unavailable
Take the CM bounce and check the status of managers , still you are facing the issue , you take the application full bounce and restart the CM , it will work .. I tried this it will work on my R12 Exa instance .
Solution 2 :
R12 Concurrent Managers down – Status show “Target node/queue unavailable
Agenda:
To start concurrent manager.
Issue:
Concurrent Managers Status shows ”Target node/queue unavailable” in Concurrent–>Manager–>Administer Screen form.
To start concurrent manager.
Issue:
Concurrent Managers Status shows ”Target node/queue unavailable” in Concurrent–>Manager–>Administer Screen form.
Solution 3:
1.
Ensure Database is Running and
Middle Tier Services are down.
2.
Connect SQLPLUS as APPS user and
run the following :
1.
EXEC FND_CONC_CLONE.SETUP_CLEAN;
2.
COMMIT;
3.
EXIT;
3.
Run AutoConfig on all tiers,
firstly on the DB tier and then the APPS tiers and webtier to repopulate the
required systemtables
4.
Run the CMCLEAN.SQL script from the referenced note below (don’t
forget to commit).
5.
Note.134007.1 – 'CMCLEAN.SQL – Non Destructive Script to Clean
Concurrent Manager Tables'
6.
Start the middle tier services
including your concurrent manager.
7.
Retest the issue.
Solution 4 :
Concurrent Processing - After Cloning All the Concurrent
Managers Do Not Start for the Clone [ID 555081.1]
Conflict Resolution Manager Shows Target Node/Queue
Unavailable [ID 732709.1]
Concurrent Managers Do Not Start After Cloning Nodes Not
Updated In Conc_queues [ID 466532.1]
EXEC FND_CONC_CLONE.TARGET_CLEAN;
Run autoconfig on dbtier then appsTier.
Run cmclean.sql script Non destructive script this
can also be tried-->>
Start all application services and check whether managers
are up.
Apply this solution in last when the above one doesnt
work.
select node_name,target_node,control_code from
fnd_concurrent_queues;
update apps.fnd_concurrent_queues set node_name = 'Node
NAME' where node_name='Existing Node Name';
select NODE_NAME,NODE_MODE,STATUS from fnd_nodes;
desc fnd_concurrent_queues
select
control_code,target_node,node_name,CONCURRENT_QUEUE_NAME from fnd_concurrent_queues;
UPDATE fnd_concurrent_queues set control_code = null;
UPDATE fnd_concurrent_queues set target_node = 'Node
Name';
UPDATE fnd_concurrent_queues set node_name = 'Node Name';
update FND_CONCURRENT_QUEUES set control_code = null where
concurrent_queue_name = 'OAMGCS_NODENAME'; -- supply the node name..(Ur
Existing Node Name)
Commit;
select control_code,target_node,node_name,CONCURRENT_QUEUE_NAME from fnd_concurrent_queues;
2. A. Most likely the node name still pointing to old
name:
1. SQ> select NODE_NAME,NODE_MODE,STATUS from fnd_nodes;
If the node name not correct then please:
2. Run the following from SQL*Plus:
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
COMMIT;
EXIT;
3. Run AutoConfig on all tiers, firstly on the DB tier and then
all the APPS tiers to repopulate the required system tables.
B. If still same issue after above steps please perform steps
from:
After Cloning all the Concurrent Managers do not start for the
cloned Instance [ID 555081.1]
