Showing posts with label Concurrent Managers issue after clone. Show all posts
Showing posts with label Concurrent Managers issue after clone. Show all posts

Wednesday, 11 April 2012

Concurrent Managers issue after clone in 11i


Concurrent managers are not coming up after the clone, having the below mentioned error in the manager log :

Starting STANDARD Concurrent Manager : 28-FEB-2008 08:25:59 Could not initialize the Service Manager FNDSM_MINEDEV_TESTMINE. Verify that mineDEV has been registered for concurrent processing. Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /d11/app/appltst/mineappl/fnd/11.5.0/bin/FNDLIBR. Check that your system has enough resources to start a concurrent manager process. Contact your system adminis : 28-FEB-2008 08:26:00 

Perform the following mentioned steps to resolve the issue:

1.       Stop the Internal Concurrent Manager.
2.       Connect to the database via SQL*Plus as the APPS user.
3.       Execute the following to alter the FNDSM trigger on FND_NODES:
CREATE OR REPLACE TRIGGER fndsm
  AFTER INSERT OR UPDATE 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;
/
4.       Ensure to commit the changes.
5.       Cleanup the FND_NODES table by executing the following:
SQL> exec FND_CONC_CLONE.SETUP_CLEAN;
6.       Run AutoConfig on each node. 


Reference:  Metalink ID 434613.1