This post is all about the concurrent manager recovery wizard which will surprise you at critical time. This wizard comes up in-built and we dont need to make any extra efforts to configure. I have provided the step by step screen shots from home page to wizard ending page.
Please utilize this wizard when your ICM does not start even though after multiple bounce. I think oracle is developing their ERP with the real time scenarios, when this CM were failed to start it just reminded me my childhood days. When i dont get up from bed my mother used to splash water in face, the same idea gonna work our here as well to wake up CM.
I have tested this in production and test when my CM failed to start and it worked like a champ. Please run this when your CM failed to start for no reason. But tried killing all FNDLIBR processed for the specific instance which causes trouble and try to restart CM. If there is no zombie processes registered in db, CM restart may help.
I can see this error in ICM logs which where helpless. No error in DB alert log. And finally i decided to run this wizard. You dont need to shutdown CM for this activity and ICM must be running while running this wizard.
Segmentation Fault - core dumped : The PROD_1027@PROD internal concurrent manager has terminated with status 139 - giving up.
========================================================================
Starting PROD_1027@PROD Internal Concurrent Manager -- shell process ID 1673
logfile=/u01/oracle/PROD/fs_ne/inst/PROD_******logs/appl/conc/log/PROD_1027.mgr
PRINTER=noprint
mailto=applmgr
restart=N
diag=N
sleep=30
pmon=4
quesiz=1
Reviver is ENABLED
Segmentation Fault - core dumped
The PROD_1027@PROD internal concurrent manager has terminated with status 139 - giving up.
How to access the concurrent manager recovery wizard?
- Log into sysadmin user
- Navigate to oracle applications manager under System administrator responsibility
- Click any menu option under Oracle Applications Manager
- Click Site Map after landing to this page.
NAvigate to Diagnostics and Repair tab and at the right side you can see Wizard.
Thats it! its tedious to find the Concurrent manager recovery wizard. Once you found it, it will make the job easier.
Issue is due to there are run away processes are registered in database which does not allow CM to start. Once i hit update button, Wizard will clear the run away processes from DB.
For more Info :
this is the same error that we received, However even after running the wizard we couldnt start the CM. Eventually it started after DB restart.
ReplyDeleteAny suggestions?