Wednesday, July 22, 2020

Target node/queue unavailable in R12.2

After creating a clone instance in R12.2, faced the below error.



There was no problem in starting or stopping the concurrent manager.

So to fix this issue, I tried running CM Recovery wizard.







Press on Next button to complete all the steps.





But this CM recovery wizard ends in vain.

So after these steps, decided to update the CM related tables manually from backend to resolve this stated error.

In the place of NODENAME replace your nodename and omit the angular brackets. You can find the nodename from fnd_nodes table.

select node_name,target_node,control_code from fnd_concurrent_queues;

update apps.fnd_concurrent_queues set node_name = '<NODENAME>' where node_name is null;

select NODE_NAME,NODE_MODE,STATUS from fnd_nodes;

select control_code,target_node,node_name,CONCURRENT_QUEUE_NAME from fnd_concurrent_queues;

UPDATE fnd_concurrent_queues set control_code = null;

select TARGET_NODE,NODE_NAME from fnd_concurrent_queues where node_name = '<NODENAME>';

select TARGET_NODE,NODE_NAME from fnd_concurrent_queues where TARGET_NODE is null;

select TARGET_NODE,NODE_NAME from fnd_concurrent_queues where TARGET_NODE = '<NODENAME>';

update fnd_concurrent_queues set NODE_NAME='<NODENAME>' where NODE_NAME='<NODENAME>';

update fnd_concurrent_queues set TARGET_NODE='<NODENAME>' where TARGET_NODE is null;

UPDATE fnd_concurrent_queues set target_node = '<NODENAME>';

UPDATE fnd_concurrent_queues set node_name = '<NODENAME>';

commit;

Once you updated the table. Try start the concurrent manager. This time the issue was fixed and everything is fine.

****************************நன்றி****************************

1 comment:

  1. This is an awesome post.Really very informative and creative contents. These concept is a good way to enhance the knowledge.I like it and help me to development very well.Thank you for this brief explanation and very nice information.Well, got a good knowledge.

    EMAIL MARKETING

    ReplyDelete

IAS Cache initialization failed

 Today I faced an Issue in R12.2 instance. The solution I followed to overcome the issue is very simple, but they are more than one solution...