Target node/queue unavailable or Concurrent Manager Issue’s

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

Solution A:

SQL> conn apps/PWD

SQL> 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 doesn’t work.

Solution B:

SQL> Desc fnd_concurrent_queues;

Note : Node Name=” Ur Existing Node Name ”

  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> 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';

  SQL> COMMIT;  //  Don’t forget

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

Ø  Retest the issue .

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

MOS ID’s :  555081.1 ,732709.1 & 466532.1

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