OPP: Output Post Processor TroubleShooting

OPP: Output Post Processor TroubleShooting

Issue 1

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

1. Shutdown Concurrent Managers
2. To ensure concurrent manager down; check there is no FNDLIBR process running.
ps -ef | grep FNDLIBR
3. Run adadmin to relink FNDSVC executable.
a. Invoke adadmin from command prompt
b. Choose option 2 (2. Maintain Applications Files menu)
c. Choose option 1 (1. Relink Applications programs )
d. Then type FND When prompted; ( Enter list of products to link (all for all products) [all] : FND )
e. Ensure adrelink is exiting with status 0
4. Start Concurrent Managers
5. Check the Output Post Processor

Issue 2

Concurrent Processing  R12 Output Post Processor Service Not Coming Up 

Reason :
If Service Manager for the node is not running.  Possible cause might be service manager definition is missing under Concurrent ->Manager ->Define form. If the Service Manager is not present/defined for a particular node,then this causes all the services provided by Service Manager like OPP,WF etc.. not to work.

1. Shutdown all the services.
Below Step 2 will create  Service Manager FNDSM
2. Log in as applmgr
cd to $FND_TOP/patch/115/sql
Run the script: afdcm037.sql
3. Relink FNDSM and FNDLIBR executables as mentioned below:
$ adrelink.sh force=y link_debug=y "fnd FNDLIBR"
$ adrelink.sh force=y link_debug=y "fnd FNDSM"
4. Run cmclean.sql
5. Start up the managers/services

Issue 3

How to restart OOP

Using System Administrator responsibility  navigate to
Concurrent-->Manager-->Administer ->query for the Output Post Processor
The Actual should equal  to the Target processes (eg: Actual=2 Target =2)

Deactivate and Activate

Alternatively you can click on Restart.
If not stopped/deactivated please check the processes and kill  and try to start
ps -ef |grep $LOGNAME | grep -v grep | grep FNDOPP

Issue 4

Output Post Processor (OPP) Log Contains Error "java.lang.OutOfMemoryError: Java heap space

- Determine what the heap size per OPP process is currently:

select DEVELOPER_PARAMETERS from FND_CP_SERVICES
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');

- The default should be:
J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m
- Increase the Heap Space per Process to 1024:
update FND_CP_SERVICES
set DEVELOPER_PARAMETERS =
'J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m'
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = 'FNDCPOPP');
- Bring the Concurrent managers down.
-Run cmclean.sql script from Note 134007.1 - CMCLEAN.SQL Non-Destructive Script to Clean Concurrent Manager Tables.
-Bring the managers up again.

OR

-Log into applications with the System Administrator responsibility.
- Navigate to Concurrent -> Program -> Define
-Query the XML Publisher Template Re-Generator program
-Set the following value for the Executable Options: -Xmx1024m
- Save changes.
- Retest the program.

Issue 5

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

This can happen on a cloned instance.

- FNDSVC should exist under FND_TOP/bin
- Bring down all application services and relink the FNDSVC through adadmin or using the below command:
adrelink.sh force=y ranlib=y "FND FNDSVC"
- Restart all applications services and restest the issue.

Issue 6

Output Post Processing Fails Due To java.lang.ThreadDeath

-Increase the value of the Concurrent:OPP Timeout profile option to 10800 seconds.
-Enable the scalability feature of XML Publisher:
a. Login as SYSADMIN
b. Responsibility: XML Publisher Administrator
c. Function: Administration
d. Set the following properties:
e. Temporary Directory
f. Use XML Publisher's XSLT processor: True
g. Enable scalable feature of XSLT processor: True
h. Enable XSLT runtime optimization: True
- Restart the Concurrent Managers so that changes take effect

Issue 7

Timeout issue with OPP

Solution:

There are 2 new profiles options that can be used to control the timeouts.

Profile Option : Concurrent:OPP Response Timeout
Internal Name : CONC_PP_RESPONSE_TIMEOUT
Description : Specifies the amount of time a manager waits for OPP to respond to its request for post processing.

Profile Option : Concurrent:OPP Process Timeout
Internal Name : CONC_PP_PROCESS_TIMEOUT
Description : Specifies the amount of time the manager waits for the OPP to actually process the request.
The value for the above profile options can be increased to avoid timeouts.
The number of processes/threads for OPP can also be increased; however the concurrent manager has to be restarted for the changes to take effect.

Some use full Note IDs

BI Publisher - Troubleshooting Oracle Business Intelligence (XML) Publisher For The Oracle E-Business Suite (Doc ID 364547.1) ****
How to Determine the Version of Oracle XML Publisher for Oracle E-Business Suite 11i and Release 12 (Doc ID 362496.1)
Concurrent Requests Fail Due to Output Post Processing (OPP) Timeout (Doc ID 352518.1)
OPP Manager Error 'ORA-600 [kqludp2]' Unable To Publish XML Reports (Doc ID 1083510.1)
Problem with OPP Where Getting XML Output Instead of PDF (Doc ID 1178457.1)
EEO Output Post Processor errors: OPP Process Timeout and OPP Response Timeout (Doc ID 458242.1)
R12 - Output Post Processor (OPP) is Down With Actual Process is 0 And Target Process is 1 (Doc ID 1075598.1)
Output Post Processor (OPP) Manager Not Working Error: APPLTMP Environment Variable is not Set (Doc ID 1381474.1)
Concurrent Processing - CP Analyzer for E-Business Suite (Doc ID 1411723.1)