Found dead process in ICM log file
There is an issue occurred on my E-Business Suite.Many concurrent mangers are not started after restarted the concurrent manger server.The Internal Manager log file shows that the following information.
Found dead process: spid=(12099), cpid=(1125806),
ORA pid=(123), manager=(0/15293)
Found dead process: spid=(12053), cpid=(1125722),
ORA pid=(104), manager=(0/14293)
This was happened due to the controlling manager was not brought down gracefully.Gracefully meaning that it was brought down when and only when, all concurrent processes are completed.I have applied the following solution to resolve this issue.
Solution:
Step1. Stop all middle tier services including the concurrent managers and verify that all APPS-Tier processes are down :
ps -fu<APPS User> | grep FND
OR
ps -fu<APPS User> | grep FND | wc -l
The command will show all processes on OS level, which are running for the Concurrent Managers. It can take some minutes until all CCM processes are stopped.
Step2. Stop the Database and verify, that all Database processes are down.
Step3. Start the database.
Step4. Execute the CMCLEAN.SQL script from the referenced note below (don’t forget to commit).
For details, please see NOTE:134007.1 – ‘CMCLEAN.SQL – Non Destructive Script to Clean Concurrent Manager Tables’.
Step5. Start the Middle Tier Services including your Concurrent Manager.
Step6. Verify the issue .
Here Second step and Third Steps are optional.Normally it s not necessary to stop the database for run the cmclean.sql.In my case the cmclean script is hanged when i do run it and its needed to restart the database.
There is an issue occurred on my E-Business Suite.Many concurrent mangers are not started after restarted the concurrent manger server.The Internal Manager log file shows that the following information.
Found dead process: spid=(12099), cpid=(1125806),
ORA pid=(123), manager=(0/15293)
Found dead process: spid=(12053), cpid=(1125722),
ORA pid=(104), manager=(0/14293)
This was happened due to the controlling manager was not brought down gracefully.Gracefully meaning that it was brought down when and only when, all concurrent processes are completed.I have applied the following solution to resolve this issue.
Solution:
Step1. Stop all middle tier services including the concurrent managers and verify that all APPS-Tier processes are down :
ps -fu<APPS User> | grep FND
OR
ps -fu<APPS User> | grep FND | wc -l
The command will show all processes on OS level, which are running for the Concurrent Managers. It can take some minutes until all CCM processes are stopped.
Step2. Stop the Database and verify, that all Database processes are down.
Step3. Start the database.
Step4. Execute the CMCLEAN.SQL script from the referenced note below (don’t forget to commit).
For details, please see NOTE:134007.1 – ‘CMCLEAN.SQL – Non Destructive Script to Clean Concurrent Manager Tables’.
Step5. Start the Middle Tier Services including your Concurrent Manager.
Step6. Verify the issue .
Here Second step and Third Steps are optional.Normally it s not necessary to stop the database for run the cmclean.sql.In my case the cmclean script is hanged when i do run it and its needed to restart the database.
0 comments:
Post a Comment