Conference ID : 39485824
Do you have any requests for future EBS - Technology Webcast Events? Please email your suggestions to ruediger.ziegler@oracle.com,subject: Topics of Interest.
AGENDA
Presentation and Demo approximately 60 - 75 minutes Q&A Session maximum 15 minutes
Web attendees can ask questions via Q&A panel Phone attendees can ask questions via Q&A panel or phone
3 Copyright 2012, Oracle and/or its affiliates. All rights reserved.
Who to ask?
3 Send
your question
Q&A panel
Program Agenda
Concurrent Manager - Troubleshooting.
1. Manager Not Running (inactive NoManager) 2. How to run cmclean(Pending Requests) 3. ICM Running , Other Managers are down 4. Only OPP & Workflow services Down 5. DBMS_LOCK Error - ICM Log 6. After CLONE Managers Down/FNDSM Errors/CONC-SM TNS FAIL 7. Managers down - Status "System Hold, Fix Manager" 8. Managers down - "Target node/queue unavailable 9. How to Enable diag=y
10
11
Administer Form
Verify ps ef | FNDLIBR process Start Concurrent Manager (adcmctl.sh) Ensure All Managers are running now.
12
Ensure Concurrent Managers are down. Collect cmclean.sql script from below document. Execute the cmclean.sql script. Start the Concurrent Manager (adcmctl.sh)
Note.134007.1 Ext/Pub CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables
13
14
15
16
Solution :
1. Check listener Status (adalnctl.sh status) 2. Stop Concurrent Manager (adcmctl.sh stop) 3. Start Listener (adalnctl.sh start) 4. Start Concurrent Manager (adcmctl.sh start)
17
18
19
Solution :
Ensure Concurrent:GSM Enabled profile is set to Y
Verify Service Manager status in Administer Form.
20
21
Solution :
Ensure Concurrent Managers are down. Ensure no FNDLIBR process running ps ef|grep FNDLIBR Run Cmclea.sql ( commit is mandatory)
22
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.
23
Solution:
Ensure Database is running Ensure Managers are down. Connect SQLPLUS as APPS user and run the following :
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT; EXIT; Run Autoconfig on DB node and then Apps Node Run $FND_TOP/patch/115/sql/afdcm037.sql script Start Services (adstrtal.sh)
24
References:
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)
25
26
Solution:
Ensure Concurrent :GSM Enabled profile is set to Y Run $FND_TOP/patch/115/sql/afdcm037.sql Go to $FND_TOP/bin
27
28
Solution:
Ensure Database is Running and Middle Tier Services are down. o Connect SQLPLUS as APPS user and run the following : 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). Note.134007.1 CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables
29
30
31
32
33
Solution:
Ensure Tmp Directory is valid. ($APPLPTMP)
Tmp Directory should have enough space.
34
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are : American_America.UTF8 '' REP-3000: Internal error starting Oracle Toolkit. REP-3000: Internal error starting Oracle Toolkit.
35
Solution:
Ensure an Xserver configured for CP server Ensure DISPLAY is set to valid Xserver Set DISPLAY in Xserver as root user and confirm Xclock is working Run xhost + From Backend CP Node Set DISPLAY as applmgr User
Run Xclock from CP Node to verify connection between CP Node and Xserver
Go to Front end and Verify DISPLAY Value If DISPLAY is incorrect in Front end then, Go to Oracle Application Manager and Change the s_display. Then Run Autoconfig Bounce Concurrent Manager.
36
37
39
40
41
42
Demonstration
43
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
44
3. 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
45
1. Connect to the concurrent manager server as Application Owner(applmgr). 2. Create an $XDO_TOP/temp and an $XDO_TOP/resource directory. 3. Create an xdodebug.cfg file in the $XDO_TOP/resource directory, containing the following 2 lines: LogLevel=STATEMENT LogDir=[full XDO_TOP]/temp 4. Restart the concurrent managers in case of single step publishing method (not required for two step publishing method). 5. Reproduce the problem.
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 xdo.log : XML Publisher Core engine debug log file xdo_...xsl : XSL-FO version of the RTF template xdo_...xml : XML data file xdo_...fo : temporary file created by the FO Engine (only RTF / XSL templates) xdo_...out : output file (may not exist in case of complete failure).
46
47
Steps:
Increase the memory from CP Definition Go to "System Administrator" responsibility. Navigate to Concurrent - > Program - > Define. Search for the report in the Concurrent Program (CP) window. Set the Options field to Xmx2048M (Note: Dont miss the dash before the X) Press Save Bounce the Concurrent Manager (optional).
48
SQL> select DEVELOPER_PARAMETERS from FND_CP_SERVICES where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME = 'FNDCPOPP'
2. The default should be: J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m 3. Increase the Heap Space per Process to 1024: SQL> 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'); SQL>Commit;
You need to restart the Concurrent Manager to make it effective. The maximim heap size should not exceed 2048.
49
There are few FoProcessing Parameters which can be fine tuned for better performance
Use XML Publisher's XSLT processor : Set this value to True Enable scalable feature of XSLT processor : Set this value to False at Site level. For large reports set this value to true at data definition level and template level. Enable XSLT runtime optimization : Set this value to True
50
Specific Situations
There are situations for which the concurrent manager process (FNDLIBR) does produce an XML data file but the post-processing of the request fails due to a different issue encountered, some of which the OPP does not even get invoked in the first place:
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. Cause: OPP Manger is Down/Deactivated. Action: Verify that the Output Post Processor is enabled and active 1. 2. 3. 4. 5. 6. 7. Profile Option "Concurrent: GSM Enabled" must be set to Y Navigate to: Concurrent -> Managers -> Define Query for Manager = 'Output Post Processor or Short Name = FNDCPOPP Check the checkbox "Enable", save the changes. Navigate to: Concurrent -> Managers -> Administer Make sure the Output Post Processor Status is not 'Deactivated',Set Status to 'Activate' if necessary. Bounce the concurrent manager for the changes to get reflected.
51
2. The Output Post Processor is running but has not picked up the request: ... +------------- 1) PUBLISH -------------+ The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status. +--------------------------------------+ 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. 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. Reference document for Process Vs Thread Doc ID 1399454.1- Tuning Output Post Processor (OPP) to Improve Performance
52
3. The concurrent manager has timed out waiting for the Output Post-processor to finish this request. ... +------------- 1) PUBLISH -------------+ The concurrent manager has timed out waiting for the Output Post-processor to finish this request. Check that there are enough Output Post-processor service processes running. More information may be found in the service process logfile. +--------------------------------------+ 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.
Action Increase the value of the Concurrent:OPP Process Timeout as follows:
1.Logon to Applications with "System Administrator" responsibility Navigate to Profile -> System 2.Query for "Concurrent:OPP Process Timeout". Set the value to 10800 sec (3 hours) 3. Query for "Concurrent:OPP Response Timeout". If the value of the Concurrent:OPP Response Timeout is 120 increase it to 240. (Value * 2)
53
Please provide the following information while raising SR with oracle support for XML Publisher Reports 1.Request log file of the failed concurrent program. 2.Out Post Processer log File
54
For complete details on all upcoming Oracle Advisor Webcast Events, please see Note 740966.1, Oracle Advisor Webcast Schedule. For EBS Technology Specific Webcasts please check Note 1186338.1. Do you have any requests for future ATG Advisor Webcast Events ? Please email your suggestions to me :
56
Oracle E-Business Suite ... BI Publisher - Business Intelligence Products (not only EBS) Core Concurrent Processing - Anything around Concurrent Processing and Concurrent Managers Core Workflow - Any Workflow isse not only E-Business Suite Diagnostic Tools - Anything around EBS Diagnostics E-Business Customizations - Your Customizations Installation - Fresh Install of the E-Business Suite Patch Review EBS - Review of Patches around the E-Business Suite Performance - EBS Performance Upgrade - EBS Upgrade User Produktivity Kit - User Productivity Kit (UPK) available for the E-Business Suite Utilities - Utilities / generic EBS DBA issues ... This is the current list for the E-Business Suite Applications Technology Group
57
58
Q&A
59
THANK YOU
for attending our Advisor Webcast!
60
61
62