Pages

Search This Blog

Thursday, October 4, 2018

Concurrent Manager Startup Issue

Issue Details:

While starting up concurrent managers with adstrtal.sh or adcmctl.sh start apps/apps_password, managers did not come up.  Verified the logfile in $APPLCSF/log/<SID_MMDD>.mgr and found below issue.


Coutine &ROUTINE has attempted to start the internal concurrent manager.  The ICM is already running.  Contact you system administrator for further assistance.afpdlrq received an unsuccessful result from PL/SQL procedure or function FND_DCP.Request_Session_Lock.
Routine FND_DCP.REQUEST_SESSION_LOCK received a result code of 1 from the call to DBMS_LOCK.Request.
Possible DBMS_LOCK.Request resultCall to establish_icm failed
The Internal Concurrent Manager has encountered an error.

Solution:

Check for any locks on concurrent managers using below query:

SELECT v$access.sid, v$session.serial# FROM v$session,v$access
WHERE v$access.sid = v$session.sid and v$access.object = 'FND_CP_FNDSM' GROUP BY v$access.sid, v$session.serial#;

Once you see the session details from the above query and kill the session.

alter system kill session 'SID,Seerial#';

After session kill, restart your concurrent managers.



No comments:

Post a Comment