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 OCTOBER 04, 2016

Applies to:

Oracle Concurrent Processing - Version 11.5.10.2 to 12.0.6 [Release 11.5 to 12]
Information in this document applies to any platform.

Symptoms

The Concurrent Manager fails to start with the 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.

 

Changes

 Recently Cloned instance.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms