Concurrent Processing - Output Post Processor is Down with Actual Process is 0 And Target Process is 1

Concurrent Processing - Output Post Processor is Down with Actual Process is 0 And Target Process is 1

After recent cloned instance find that actual process of concurrent manager Output Post Processor is 0 and target process is 1.

Cause:

Executable FNDSVC is not generated / relinked properly in the new target instance after cloning.

Due to this OPP concurrent manager was not coming up. This can be verified from backend command line , which returns nothing.

ps -ef | grep applmgr | grep FNDSVC

Solution:

To implement the solution, please execute the following steps:

1. Telnet to application tier server via OS user applmgr, and source the env file
$APPL_TOP/APPS<SID>_hostname.env.

2. Shutdown concurrent server via command adcmctl.sh under
$COMMON_TOP/admin/scripts/<context_name>

3. To ensure concurrent manager down; check there is no FNDLIBR process running.
ps -ef | grep applmgr | grep FNDLIBR

4. Run adadmin to relink FNDSVC executable.

1. Invoke adadmin from command prompt
2. Choose option 2 (2. Maintain Applications Files menu)
3. Choose option 1 (1. Relink Applications programs )
4. Then type "FND" When prompted; ( Enter list of products to link ('all' for all products) [all] : FND )
5. Ensure adrelink is exiting with status 0

5. Start Concurrent Managers using adcmctl.sh

6. Retest the issue.

7. Migrate the solution as appropriate to other environments.

Reference metalink Doc ID 858813.1