Fixing Concurrent Manager Crashes After EBS R12.2 Cloning

We finished a rapid clone of our Oracle EBS R12.2 instance last night, but the Concurrent Managers refused to come up. Every time we kicked off the startup scripts, the ICM (Internal Concurrent Manager) immediately went into a deactivated status.

1. Checking the Real Logs

Instead of guessing, I went straight to the application tier diagnostic logs. The ICM log layout is found under your specific log directories:

$APPLCSF/$APPLLOG/NAME_MMDD.mgr

Inside, the log clearly stated that it could not initialize due to old node configurations stuck in the database layout tables. To clear out the stale configuration entries from the previous environment, I logged into SQL*Plus as the APPS user and ran the clean scripts:

EXEC FND_CONC_CLONE.SETUP_CLEAN;

2. Regenerating the Environment

Once the setup cleanup command executed successfully, I had to run Autoconfig to completely rebuild the system profile values and directory layouts:

sh $ADMIN_SCRIPTS_HOME/adautocfg.sh

After Autoconfig finished with a successful status code 0, I brought the managers back online using the standard control utility line script:

sh $ADMIN_SCRIPTS_HOME/adcmctl.sh start apps/apps_password

The Internal Concurrent Manager caught the correct database tables instantly and stayed up. Always remember to clear out stale configuration contexts post-clone!