My Oracle Support Banner

Concurrent Manager FNDCRM Down / Crashed All Scheduled Concurrent Programs Are Stuck Pending/Scheduled Pending/Standby (Doc ID 1604300.1)

Last updated on APRIL 14, 2023

Applies to:

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

Symptoms

 All scheduled concurrent requests are stuck either with Pending/Scheduled or Pending/Standby status for longer time. It is found that the Conflict Resolution Manager ( FNDCRM ) has crashed with the following error:

Conflict Resolution Manager started with concurrent process id 262493
Found uncached user: -1

:

Found uncached user: 3725

27-NOV-2013 23:28:46 :

27-NOV-2013 23:28:46 : An error occurred in routine rxcrm_req_resolve.

27-NOV-2013 23:28:46 : Rolling back database state

27-NOV-2013 23:29:16 :

27-NOV-2013 23:29:16 : An error occurred in routine rxcrm_req_resolve.

27-NOV-2013 23:29:16 : Rolling back database state

27-NOV-2013 23:29:46 :

27-NOV-2013 23:29:46 : An error occurred in routine rxcrm_req_resolve.

27-NOV-2013 23:29:46 : Rolling back database state

27-NOV-2013 23:30:16 :

27-NOV-2013 23:30:16 : An error occurred in routine rxcrm_req_resolve.

27-NOV-2013 23:30:16 : Rolling back database state

27-NOV-2013 23:30:46 :

27-NOV-2013 23:30:46 : An error occurred in routine rxcrm_req_resolve.

27-NOV-2013 23:30:46 : Rolling back database state
Quitting after too many failures

Changes

It could be possible that the FND_CONFLICTS_DOMAIN table is grown huge.

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.