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

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

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;