My Oracle Support Banner

CP Managers fail to start up and CPADMIN: Clean concurrent processing tables hangs (Doc ID 2719359.1)

Last updated on OCTOBER 12, 2020

Applies to:

Oracle Concurrent Processing - Version 12.2 and later
Information in this document applies to any platform.

Symptoms

When starting the Concurrent Processing (CP) server with the adstrtal.sh / adcmctl.sh script, all E-Business Suite (EBS) concurrent managers do not start up.
Other observed symptoms:

. The utility CPADMIN: 'Clean concurrent processing tables' hangs

. The Concurrent Manager Recovery Wizard completes successfully, with any errors or warning.

.  The Internal Concurrent Manager (ICM) log file shows that the managers shut down quickly after starting up, displaying dead manager processes for two specific Service Managers, the 'SFM Event Manager Queue Service' and the 'Output Post Processor' :

"Internal Concurrent Manager started : 12-OCT-2020 10:49:55
+---------------------------------------------------------------------------+
12-OCT-2020 10:49:55 - Checking ICM sleep

                  Process monitor session started : 12-OCT-2020 10:49:55
Found dead process: spid=(679), cpid=(469876), Service Instance=(1071)
Found dead process: spid=(2789), cpid=(470049), Service Instance=(1168)
Found dead process: spid=(689), cpid=(469884), Service Instance=(1168)
Found dead process: spid=(688), cpid=(469883), Service Instance=(1168)
Found dead process: spid=(686), cpid=(469881), Service Instance=(1168)
sh: line 34: 14457: Killed
The ABCD_1234@WXYZ internal concurrent manager has terminated with status 265 - giving up."

 

Changes

 Database upgrade and CPU patches applied two weeks before this event

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


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