在项目上遇到这样一个情况，从一个有双节点的EBS环境中克隆的一套系统测试系统的时候，当时在测试一个报表的时候出现警告，看日志说是内部管理器有问题，我就依此找到了内部管理器，发现内部管理器节点为空，于是找同事帮忙，定义新的节点，路径为：系统管理员/并发/管理器/定义/，定义方法相信接触的EBS的人都知道的，最后重新启动adcmctl.sh应用服务即可。非正常内部管理器和定义内部管理器如下图所示：
users reports back that reports are not running with no manager error (see below), and when you check manager status, all managers have Description- Target Node/Queue Unavailable
Solution One:
1. . Run the following in SQL*Plus:
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
2. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers, to repopulate the required system tables.
Db Tier:
cd $ORACLE_HOME/appsutil/scripts/<inst>/adautocfg.sh
Apps Tier:
cd $ADMIN_SCRIPTS_HOME/adautocfg.sh
Solution Two:
1. Run cmclean.sql with Apps tier down
2. restart all services and check
Solution Three (if All else fails, check all the details below:)
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> select TARGET_NODE,NODE_NAME from fnd_concurrent_queues where node_name='<Existing Node Name>’;
SQL> select TARGET_NODE,NODE_NAME from fnd_concurrent_queues where TARGET_NODE='<Existing Node Name>’;
SQL> update fnd_concurrent_queues set NODE_NAME='<Node Name>’ where NODE_NAME='<Source/Existing Node Name>’;
SQL> update fnd_concurrent_queues set TARGET_NODE='<Node Name>’ where TARGET_NODE='<Source/Exixting Node Name>’;
SQL> UPDATE fnd_concurrent_queues set target_node = ‘<Node Name>’;
SQL> UPDATE fnd_concurrent_queues set node_name = ‘<Node Name>’;
SQL> Commit;
SQL> select control_code,target_node,node_name,CONCURRENT_QUEUE_NAME from fnd_concurrent_queues;
SQL>select TARGET_NODE,NODE_NAME from fnd_concurrent_queues where node_name='<Node Name>’;
SQL>select TARGET_NODE,NODE_NAME from fnd_concurrent_queues where TARGET_NODE='<Node Name>’;
Solution four:
SQL> set linesize 1000;
SQL> column CONTROL_CODE format A15
SQL> select CONCURRENT_QUEUE_NAME, CONTROL_CODE , TARGET_NODE, NODE_NAME from FND_CONCURRENT_QUEUES where concurrent_queue_name like ‘OAMGCS_%’;
Sample Output:
CONCURRENT_QUEUE_NAME CONTROL_CODE TARGET_NODE NODE_NAME
—————————— ————— —————————– ——————————
OAMGCS_SUPTEBSAL1 E SUPTEBSAL1
To implement the solution, please execute the following steps:
1. Please set control_code to null for the OAMGCS concurrent queue on the specific node that is affected by this issue.
SQL> update FND_CONCURRENT_QUEUES
set control_code = null
where concurrent_queue_name = ‘OAMGCS_<hostname>’; <Ur Existing Node Name>
2. Make sure the Target_node is correct for the OAMGCS manager:
SQL> update FND_CONCURRENT_QUEUES
set TARGET_NODE='<correct node >’
where CONCURRENT_QUEUE_NAME=’OAMGCS_<hostname>’;
SQL> commit;
References:
Conflict Resolution Manager Shows Target Node/Queue Unavailable [ID 732709.1]
OAM Generic Collection Service shows State: “The target node/queue unavailable”. [ID 393706.1]
After Cloning all the Concurrent Managers do not start for the cloned Instance [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]
Summary of Possible Reasons and Solutions for the Problem Where All Concurrent Requests Stuck in Pending Phase [ID 182154.1]
Output Post Processor is Down with Actual Process is 0 And Target Process is 1 [ID 858813.1]
Using Load-Balancers with Oracle E-Business Suite Release 12 [ID 380489.1]
Documentation For Specific Load Balancer Hardware [ID 727171.1]
Sharing The Application Tier File System in Oracle E-Business Suite Release 12 [ID 384248.1]
Add new node to application —- 384248.1
Common Error: Concurrent Manager shows “Target Node/Queue Unavailable “