Step-1
you need to check log file and find out more details about possible errors from log file.If log file not helps than you can enable trace and can see what is issue.
Step-2
If Log file shows like this than do below step.
Log file detailed below.....
req log:pointing to opp issue
check opp log:
[11/28/11 8:03:09 AM] [UNEXPECTED] [44537:RT5646259] java.lang.NumberFormatExcep
tion: For input string: "DESCRIPTION="
at java.lang.NumberFormatException.forInputString(NumberFormatException.
java:48)
at java.lang.Integer.parseInt(Integer.java:447)
at java.lang.Integer.parseInt(Integer.java:497)
at oracle.apps.xdo.generator.pdf.PDFGenerator.setFont(PDFGenerator.java:
629)
at oracle.apps.xdo.generator.pdf.PDFGenerator.setProperties(PDFGenerator
.java:468)
at oracle.apps.xdo.generator.ProxyGenerator.setProperties(ProxyGenerator
.java:1373)
at oracle.apps.xdo.template.fo.FOHandler.startElement(FOHandler.java:262
solution:
Bounce OPP concurrent manager.
Step-3
If issue persists than do follow below steps.
Concurrent: OPP Process Timeout - changed from 300 to 600 (10 minutes)
Java heap size - changed from 512 to 1024.
Report ran successfully
Identify the OPP log file :
1.Directly from the file system based after identifying the corresponding OPP log file
name using the following SQL statement:
SELECT fcpp.concurrent_request_id req_id, fcp.node_name, fcp.logfile_name
FROM fnd_conc_pp_actions fcpp, fnd_concurrent_processes fcp
WHERE fcpp.processor_id = fcp.concurrent_process_id
AND fcpp.action_type = 6
AND fcpp.concurrent_request_id = &&request_id
2.Via the Forms application:
1. Login to the application as SYSADMIN
2. Responsibility: System Administrator
3. Function: Concurrent --> Manager --> Administration
4. Select the Output Post Processor
5. Click on the Processes button
6. Select the Concurrent Process which was active during the time that the request ran
7. Click on the Manager Log button to open the Output Post Processor log file
3.Via the Oracle Application Manager (OAM)
1. Login to the application as SYSADMIN
2. Responsibility: System Administration
3. Function: Oracle Applications Manager --> Concurrent Managers
4. Select the Output Post Processor Service and click on View Details
5. Click on View Processes
6. Select the Concurrent Process which was active during the time that the request ran
7. Click on the Log button to open the Output Post Processor log file
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');
TO KNOW OPP log :
=================
cd $APPLCSF/$APPLLOG
grep 1731722 FNDOPP*
grep Error* FNDOPP*
No comments:
Post a Comment