Solution 1 :
take the CM bounce and check the status of managers , still you are facing the issue , you take the application full bounce and restart the CM , it will work .. I tried this it will work on my R12 Exa instance .
note : check the application listner is up and running , if not start the adalnctl.sh start.. then check the issue...
Solution 2 :
R12 Concurrent Managers down – Status show “Target node/queue unavailable
Agenda:
To start concurrent manager.
Issue:
Concurrent Managers Status shows ”Target node/queue unavailable” in Concurrent–>Manager–>Administer Screen form.
Solution:
To start concurrent manager.
Issue:
Concurrent Managers Status shows ”Target node/queue unavailable” in Concurrent–>Manager–>Administer Screen form.
Solution:
- Ensure Database is Running and Middle Tier Services are down.
- Connect SQLPLUS as APPS user and run the following :
- EXEC FND_CONC_CLONE.SETUP_CLEAN;
- COMMIT;
- EXIT;
- Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and webtier to repopulate the required systemtables
- Run the CMCLEAN.SQL script from the referenced note below (don’t forget to commit).
- Note.134007.1 – 'CMCLEAN.SQL – Non Destructive Script to Clean Concurrent Manager Tables'
- Start the middle tier services including your concurrent manager.
- Retest the issue.
Solution 3 :
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;
Thanks
Srini
No comments:
Post a Comment
No one has ever become poor by giving