Unable to Start Concurrent Manager, Internal Manager Creates Zero Byte Log File.
Symptoms:
Problem Statement:
When attempting to start concurrent manager then none of the concurrent manager is starting and Internal manager creates a zero byte log file. There is no error displayed while starting the concurrent manager.
Actual Process = Target Process = 0 ( For Every Concurrent Manager )
Cause:
Executable "sh" is not pointing to the correct "sh".
Connect to appsTier : Concurrent Manager Node
$ which sh
$FND_TOP/bin/sh
It should point to operating system "sh".
Solution:
To implement the solution, please execute the following steps:
1.) Connect to appsTier : Concurrent Manager Node
$ chmod 644 $FND_TOP/bin/sh
2.) Run the CMCLEAN.SQL script from the referenced note below (don't forget to commit).
=========================
NOTE:134007.1 - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables
=========================
3.) Start the concurrent manager.
4.) Retest the issue.
Symptoms:
Problem Statement:
When attempting to start concurrent manager then none of the concurrent manager is starting and Internal manager creates a zero byte log file. There is no error displayed while starting the concurrent manager.
Actual Process = Target Process = 0 ( For Every Concurrent Manager )
Cause:
Executable "sh" is not pointing to the correct "sh".
Connect to appsTier : Concurrent Manager Node
$ which sh
$FND_TOP/bin/sh
It should point to operating system "sh".
Solution:
To implement the solution, please execute the following steps:
1.) Connect to appsTier : Concurrent Manager Node
$ chmod 644 $FND_TOP/bin/sh
2.) Run the CMCLEAN.SQL script from the referenced note below (don't forget to commit).
=========================
NOTE:134007.1 - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables
=========================
3.) Start the concurrent manager.
4.) Retest the issue.
No comments:
Post a Comment