Target node/queue unavailable or Concurrent Manager Issue’s after DB -Refresh / Cloning :

Target node/queue unavailable or Concurrent Manager Issue’s after Cloning or DB-Refresh:

Solution A:

Step 1: Take down application

SQL> EXEC FND_CONC_CLONE.TARGET_CLEAN;

Step 2: Run cmclean.sql script 

Step 3:  Run autoconfig on dbTier then appsTier.

Start all application services and check whether managers are up.

Solution B:

Apply this solution in last when the above one doesn’t work.

SQL> select node_name,target_node,control_code from fnd_concurrent_queues;

SQL> update apps.fnd_concurrent_queues set node_name = 'Node NAME' where node_name='Existing Node Name';

SQL> select NODE_NAME,NODE_MODE,STATUS from fnd_nodes;

SQL> desc fnd_concurrent_queues

SQL> select control_code,target_node,node_name,CONCURRENT_QUEUE_NAME from fnd_concurrent_queues;

SQL> UPDATE fnd_concurrent_queues set control_code = null;

SQL> UPDATE fnd_concurrent_queues set target_node = 'Node Name';

SQL> UPDATE fnd_concurrent_queues set node_name = 'Node Name';

SQL> update FND_CONCURRENT_QUEUES set control_code = null where concurrent_queue_name = 'OAMGCS_NODENAME'; -- supply the node name..(Ur Existing Node Name)

SQL> Commit;

SQL> select control_code,target_node,node_name,CONCURRENT_QUEUE_NAME from fnd_concurrent_queues;

+++++++++Manjunatha++++++

732709.1,555081.1 & 466532.1

++++++++++++++++++++++