Internal Concurrent Manager Startup has Terminated With Status 139 Database Error ORA-28 : opiodr aborting process unknown ospid (Doc ID 1577696.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Concurrent Processing - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

Symptoms

Start up of EBS system, the concurrent manager can not startup.

The ICM log shows the following error message:

The ICM has lost its database connection and is shutting down.
Spawning reviver process to restart the ICM when the database becomes available again.

Spawned reviver process 19848.

List of errors encountered:
.............................................................................

_ 1 _
Routine AFPCMT encountered an ORACLE error. ORA-01012: not logged on
.

Review your error messages for the cause of the error. (=)

_ 2 _
Routine AFPSMG encountered an ORACLE error. ORA-01012: not logged on
.

Review your error messages for the cause of the error. (=)

_ 3 _
Routine AFPEIM cannot create a process ID for your concurrent manager
process ORACLE error 1012 in FDUUID

Cause: FDUUID failed due to ORA-01012: not logged on.

The SQL statement being executed at the time of the error was: SELECT
FND_CONCURRENT_PROCESSE
sh: line 68: 19607 Segmentation fault FNDLIBR FND CPMGR "FNDCPMBR sysmgr=\"\" sleep=30 pmon=4 quesiz=1 diag=N logfile=/u03/..../conc/log/PRODB_0814.mgr " <<STOP
$unpw
STOP

The PRODB_0814@PRODB internal concurrent manager has terminated with status 139 - giving up.

Cause: get_cart_appl failed due to ORA-00028: your session has been killed.

The SQL statement being executed at the time of the error was: SELECT BASEPATH FROM FND_APPLICATION WHERE APPLICATION_ID = :I
Could not establish connection to Service Manager. afpsmcsm exiting with error 132.

Starting FNDCPOPP Concurrent Manager : 14-AUG-2013 10:41:20
The Internal Concurrent Manager has encountered an error.

Review concurrent manager log file for more detailed information. : 14-AUG-2013 10:41:20


Database Alert log file show the following error:

Incremental checkpoint up to RBA [0x60.5899b.0], current log tail at RBA [0x61.11eb5.0]
Wed Aug 14 11:05:48 2013
Completed checkpoint up to RBA [0x61.2.10], SCN: 5965605259035
Wed Aug 14 11:09:22 2013

Wed Aug 14 10:33:20 2013
ORA-28 : opiodr aborting process unknown ospid (20034_47128617884864)

Changes

 

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