Routine FND_DCP.REQUEST_SESSION_LOCK received a result code of 1 from the call to DBMS_LOCK.Request.

Dear Folks,

Recently, we faced an issue with concurrent managers in 11i instance . We couldn't able to start them. Gone through database bounce and cm cleanup. But neither of them fixed it.

We looked up manager log file and found below errors.

Routine &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.

Fix

===

Look for object FND_CP_FNDSM locks.

SQL> 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#;   2    3    4

       SID    SERIAL#

---------- ----------

      1105         27

       626         23

USERNAME           SID    SERIAL# STATUS

----------- ---------- ---------- --------

ACTION

----------------------------------------------------------------

MODULE

------------------------------

APPS              1105         27 INACTIVE

FNDSM@nchuilmrebsa01.kermar.tcs

 (TNS V1-V3)

USERNAME           SID    SERIAL# STATUS

----------- ---------- ---------- --------

ACTION

----------------------------------------------------------------

MODULE

------------------------------

APPS               626         23 INACTIVE

Kill above sessions with immediate option and start CM services. They will be up.

Thanks.