Administrator
|
Executable:POXCON - PO Document Approval Manager Program
Executable:RCVOLTM - Receiving Transaction Manager
Executable:INCTM - Inventory Remote Procedure Manager
These are not related with Standard Manager.
you can kill the remaining processes after the adstpall returns with exit status of 0 , but you can review their log files for further diagnostics as well.
For you main issue, I mean "standard manager and inventory managers, won't start. " , I believe it is related with the Concurrent PCP Instance Check.. It should be off, if you are not using Parallel Concurrent Processing and since you have only a single Apps Tier you can't just have Parallel Concurrent Processing.
I suggest you to take the steps like I did ->
As for the solution: I did set set "Concurrent PCP Instance Check" to OFF. (it was ON before)
Then I relinkled FNDLIBR binaries and executed cmclean.sql
After that I saw that the error that we were getting, changed.
Standard manager could not start fully. (The target was 10, but the actual was 1 , 2 , and 3 sometimes)
It was obvious that there was some concurrent request issue. A problematic concurrent request assigned to the standard manager queue..
Anyways, I fixed it using the solution documented in Standard Manager Not Starting After Clone (Doc ID 1390758.1)
|