Output Post Processor Down : Actual 0 Target 1

Output Post Processor Down : Actual 0 Target 1

Some times Output Post Processor is not start up and it shows Actual and Target are showing different values when we query for Output Post Processor.

The log files shows that no error message.In this case apply the following possible solution for starting the OPP.

1. Shutdown the internal manager by using adcmctl.sh stop apps/****
2. Make sure there is no FNDLIBR processe running:
            $ ps -ef| grep FNDLIBR OR ps -ef|grep applprod|grep FNDLIBR
3. If there is any FNDLIBR processe please kill it $ kill -9 pid
4. Run cmclean.sql script as document from Note 134007.1
5. Restart the internal manager by using adcmctl.sh start apps/*****

Now see the current status of Output Post Processor if its up then no need to do anything and issue will be resolved..

but in some cases in it will not up after cmclean ans status will same as it before then simply kill the output post processor and issue will be resolved.


Solution:

1.  System Administator > Concurrent > Manager > Administer
2.  Query "Output Post Processor" -> Processes button
           Get the sytem id of "Output Post Processor"
3.  ps -ef|grep [system id]
4.  kill -9 [system id] in Unix
5.  System Administator > Concurrent > Manager > Administer
6.  Query "Output Post Processor" -> Restart button

and now see the status it will be resolved..