concurrent managers were not starting

Once after doing Rapid cloning some of concurrent managers were not starting.
The issue was that the node was wrongly defined as source node in Administer Manager screen.
Then i checked in the FND_NODES table which wrongly had the source nodes as well apart from the target nodes.

I performed the following action plan which resolved the issue->

* Shutdown the apps services

* EXEC FND_CONC_CLONE.SETUP_CLEAN;

   COMMIT;

   EXIT;

adrelink.sh force=y link_debug=y "fnd FNDLIBR"

adrelink.sh force=y link_debug=y "fnd FNDFS"

adrelink.sh force=y link_debug=y "fnd FNDCRM"

adrelink.sh force=y link_debug=y "fnd FNDSM"

* Ran AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers.

* Start the apps services.

Actually FND_CONC_CLONE.SETUP_CLEAN clears up the tables with nodes information and when we run autoconfig, it repopulates these tables with correct node information.