Concurrent Manager Not Starting After Cloning
Solution:
- Shutdown the application services
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
- Ran AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers.
- Start the application 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.
No comments:
Post a Comment