Concurrent Processing - The Concurrent Manager Fails to Start on GSM Enabled Due to DBMS_LOCK.Request ResultCall Failed to Establish ICM
(Doc ID 245563.1)
Last updated on JUNE 30, 2022
Applies to:Oracle Concurrent Processing - Version 126.96.36.199 to 12.2.7 [Release 11.5 to 12.2]
Information in this document applies to any platform.
Reviewed for Relevance 9 Mar 18.
The Concurrent Manager fails to start with error:
The ICM is already running. Contact you system administrator for further assistance.
A fpdlrq 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.
Recently Cloned instance.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!