Core Concurrent Processing - EBS (MOSC)

MOSC Banner

ICM not starting after going down

edited Mar 25, 2013 9:58PM in Core Concurrent Processing - EBS (MOSC) 6 commentsAnswered

I get the below issue always when ICM goes down and reviver tries to start it up. Even manually starting also throws the same issue.

If I do CMCLEAN and start, it will come up but for that downtime is needed, but BUT should get started by reviver itself which is not happening. please find log file below.

          logfile=/pa02/ebiz/apps/apps_st/comn/admin/AEPRD_gitsaepap01/log/AEPRD1_0319.mgr
          PRINTER=noprint
           mailto=applaeprd
          restart=N
             diag=N
            sleep=30
             pmon=4
           quesiz=1
          Reviver is ENABLED
 
sh[34]: 24510548 Segmentation fault(coredump) 
The AEPRD1_0319@AEPRD1 internal concurrent manager has terminated with status 139 - giving up.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

EBS Concurrent Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center