My Oracle Support Banner

FAQ: EBS Concurrent Processing Performance and Best Practices (Doc ID 1373727.1)

Last updated on OCTOBER 25, 2019

Applies to:

Oracle Concurrent Processing - Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]
Oracle Application Object Library - Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.

Purpose

This Document will address the questions and answers related to EBS Concurrent processing Performance and Best Practices

Questions and Answers

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Questions and Answers
 What are the Focus areas in an AWR report?
 How to get the trace information for a custom program?
 If the cache size is 10 and out of them 9 have completed and 1 is running long, in the next cycle will it cache 10 more or will it take up 9 more as one is already running?
 Can one specify the default trace location?
 When running 'Gather Schema Statistics' setting higher the estimate percent % will give better performance?
 Why the requests are not getting killed from the backend once cancelled from the Frontend?
 Please share any note that gives the details of the things that happen in background when running a concurrent request?
 What is the recommended number of rows that should be maintained in the fnd_concurrent_requests table to avoid performance problems?
 Should one need to run the Concurrent Manager Recovery in OAM after increasing the cache size = 2 * target process followed by bounce?
 Is It GOOD to run Gather Schema Statistics on FND tables? 
 What is the cause for getting locks on a Request file?
 When setting the Purge program parameters, there is a parameter called 'Purge Other'.  What is this referring to?
 Why do we need to analyze all index column stats after running gather schema stats.  In other words, why gather schema stats doesn't gather column stats?
 We recently upgraded the database 11.2.0.1 to 11.2.0.2 and observed that jobs submitted though CONCSUB are in the PENDING STANDBY status for very long time.
 How often is it recommended to run the Analyze All Index column Statistics?
 Is it recommended to schedule a job that gets statistics a 100% of estimate percent on the tables listed with the package FND_STATS?
 If we want to run Analyze on all the tables in order to get statistics chained rows, will it cause any problems to do this, if we run Gather Schema Statistics afterwards?
 what are the other options for the entity parameter of the FNDCPPUR job (presentation just showed all)?
 Can we run the statistics on these FND tables from backend?
 Where can I set the work shift?
 What happens if a job runs and it doesn't finish during the workshift?  Will the manager not finish the job till the next workshift?
 Is performance affected when we have all the managers active 24 hrs every day?
 By giving only the time for which we want our specialized manager to work in the Description, will it work?
 When 2 requests are being processed, we see that one ouput gets created with 0 filesize and the 2nd one containing data/content from xml files of both the requests
 The scalable flag help the large reports to end creating temp files, but could affect the small ones creating this tmp files?
 What is RAC?
 Can we use this feature to set the job to run on a specific instance in R12.1, even if we run the SCAN feature of 11.2 DB version?
 What is that target instance used for?
 Is the Target RAC not available in 11.5.10.2?
 Where can I get the the usage for all profile option?
 What is the performance percentage difference between pipe vs QUEUE type.   PIPE has faster performance.  Does it give double or triple performance than queue?
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.