Professional Documents
Culture Documents
North America:
1866 966 9439
International (UK): Do you have any requests for future EBS - Technology
+44 (0) 1452 562 665 Webcast Events? Please email your suggestions to
ruediger.ziegler@oracle.com,subject: Topics of Interest.
Conference ID : 39485824
• Q&A Session
maximum 15 minutes
3 Send
your question
Q&A panel
1
type your question here
Note:
You can view this info anytime using WebEx menu from your WebEx-Session :
Error#1:
Error#2:
Could not contact Service Manager FNDSM_DHSRVMDS518_SDBA. The TNS alias could not be located, the listener process
on DHSRVMDS518 could not be contacted, or the listener failed to spawn the Service Manager process.
Error#3:
Cause: cleanup_node failed due to ORA-01427: single-row subquery returns more than one row
ORA-06512: at "APPS.FND_CP_FNDSM", line 29
ORA-06512: at line 1.
• Concurrent Processing - After Cloning all the Concurrent Managers do not start for the cloned
Instance (Doc ID 555081.1)
• ICM log file shows 'CONC-SM TNS FAIL', 'Call to PingProcess failed', and/or 'Call to StopProcess
failed' for FNDCPGSC/FNDOPP (Doc ID 1312632.1)
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
o Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and webtier to repopulate the required system
tables
o Run the CMCLEAN.SQL script from the referenced note below (don't forget to commit).
XML_REPORTS_XENVIRONMENT is :
/u01/app/protoora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb
''
Go to Concurrent Program -> Define form -> Query for Concurrent Program Enable Trace
prompt
accept request prompt 'Please enter the concurrent request id for the appropriate concurrent program:'
prompt
Syntax :
Troubleshooting
1. Directly from the file system based after identifying the corresponding OPP log file name using the following SQL
statement:
Note: The SQL statement will only return data for those Concurrent Requests having a Layout specified (Upon
Completion... window).
The XDO log consist of complete debug information generated by XML Publisher Core engine. Follow the steps given
below to enable debug
Note: The xdodebug.cfg file can also be created in the $AF_JRE_TOP/jre/lib OR $AF_JRE_TOP/lib directory.
With the above steps several debug files will be created under the $XDO_TOP/temp directory after reproducing the
Problem
Symptoms: The Report completes with an Error The log file includes a message similar to the following:
+------------- 1) PUBLISH -------------+
Beginning post-processing of request 744134 on node R12P660 at 10-JAN-2012
14:50:47. Post-processing of request 744134 failed at 10-JAN-2012 14:51:15 with the
Error message: One or more post-processing actions failed. Consult the OPP service log for
details.
OR
'****Warning!!! Due to high volume of data, got out of memory exception...***
'****Please retry with scalable option or modify the Data template to run in scalable mode...***
OR
java.lang.OutOfMemoryError: Java heap space
Steps:
1.Check the current OPP JVM Heap size using following SQL query
SQL>Commit;
You need to restart the Concurrent Manager to make it effective. The maximim heap size should not
exceed 2048.
There are few FoProcessing Parameters which can be fine tuned for better performance
1. The Output Post Processor is not running or does not pick up the request:
... +------------- 1) PUBLISH -------------+
Unable to find an Output Post Processor service to post-process request 260006.
Check that the Output Post Processor service is running.
+--------------------------------------+ ...
The OPP log file cannot be determined using the SQL statement described earlier, as the OPP did not perform any action of the given
request.
Action: Verify that the Output Post Processor is enabled and active
Cause: The number of concurrent requests that the Output Post Processor can handle in parallel depends upon the number of
Processes and the number of Threads Per Process. The default values are 2 Processes and 5 Threads Per Process so a total of
10 reports can be processed in parallel. In case there are other concurrent requests running which have already invoked the
OPP then it might happen that no additional requests can be picked up for a period of time.
Action:
1.Logon to Applications with "System Administrator" responsibility
2.Navigate to Concurrent -> Manager -> Define
3.Query for "Output Post Processor"
4.Click on "Work Shifts" and Increase the number of increase the number threads from 5 to 10
oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5
to
oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=10
5.Bounce the concurrent Manager for the changes to get reflected.
The concurrent manager process has successfully invoked the OPP but it a timeout is encountered as the OPP takes too long to
complete the job
Cause: Once the Output Post Processor picks up the request, the BI Publisher engine is invoked to generate the final output file. The
time that this takes will depends on various elements such as size of the XML data file, complexity of the template, performance of
the server.By default a timeout will occur if it takes longer then 300 seconds (5 min.) for the BI Publisher engine to generate the
output file. The concurrent request will complete with status Warning and the request log file will contain above error Message.
For complete details on all upcoming Oracle Advisor Webcast Events, please see
Note 740966.1, Oracle Advisor Webcast Schedule.
Do you have any requests for future ATG Advisor Webcast Events ?
Please email your suggestions to me :