After ATG RUP 5 Concurrent Managers Fail to Start

Last week I have installed the ATG RUP 5 on my TEST environment. Everything goes smooth, all additional patche applied successfully, the application startup succesfully, great.... Today, I decide to make some order in this TEST environment and I run FND_CONC_CLONE.setup_clean to clean FND_NODES and all tables that refilled by autoconfig. Afterwards, autoconfig on DB tier and APPS tier. I checked the FND_NODES table and it looks like it populated successfully (without the old nodes from source environment...) I run the adstrtall script to startup apps tier and the Concurrent Managers didn't startup! The error mesasge I got was: Could not initialize the Service Manager FNDSM_[SERVER_NAME]_[ENV_NAME]. Verify that [SERVER_NAME] has been registered for concurrent processing. Routine AFPEIM encountered an error while starting concurrent manager.... The cause of this problem is the change of FNDSM trigger in ATG RUP 5. ==================================================== The new FNDSM trigger code is: CREATE OR REPLACE TRIGGER fndsm AFTER INSERT ON FND_NODES FOR EACH ROW BEGIN if ( :new.NODE_NAME <> 'AUTHENTICATION' ) then if ( (:new.SUPPORT_CP='Y') or (:new.SUPPORT_FORMS='Y') or (:new.SUPPORT_WEB='Y') ) then fnd_cp_fndsm.register_fndsm_fcq(:new.NODE_NAME); end if; if (:new.SUPPORT_CP = 'Y') then fnd_cp_fndsm.register_fndim_fcq(:new.NODE_NAME); end if; end if; END; ==================================================== When we run autoconfig on db tier, new row inserted into FND_NODES but FNDSM and FNDIM are not created since db tier not supported CP/FORMS/WEB. When we run autoconfig on apps tier, this columns are updated to 'Y' but FNDSM trigger is not run because it is fired for insert and not for update. The Solution is : 1) Recreate the FNDSM trigger same as before but add "AFTER INSERT OR UPDATE ON FND_NODES". 2) Run: exec FND_CONC_CLONE.setup_clean; (with apps) 3) Run autoconfig on db tier and apps tier (in this order) 4) Startup apps tier. There is no patch at this time to fix this probem, but when ATG RUP 6 will be available it will contain a fix to FNDSM trigger. Full details in Metalink note 434613.1. Cheers, Aviad