Concurrent Processing Tips & Tricks & CP Analyzer Update

Concurrent Processing Tips & Tricks & CP Analyzer Update

Did you know?

Tuning concurrent processing largely depends on customers' specific business needs. While Support is unable to provide specific recommendations that address all circumstances, we can certainly provide the guidance which helps you make decisions.

Be sure to check out the following documents to understand the considerations for healthy Concurrent Processing:

  • Doc ID 1057802.1 Best Practices for Performance for Concurrent Managers in E-Business Suite
  • Doc ID 986272.1 How To Performance Tune The Concurrent Processing Server

Purging

We suggest you run the FNDCPPUR "Purge Concurrent Request and/or Manager Data" request on ALL instances during hours of low workloads. Doing this regularly and after hours will decrease the contention on the tables running against daily processing. For more information on basic usage for running the Purge program and code fixes, please reference: Doc ID 822368.1 Concurrent Processing - How To Run the Purge Concurrent Request FNDCPPUR, Which Tables Are Purged, And Known Issues Like Files Are Not Deleted From File System or Slow Performance.

Tip: Discuss with the functional teams for determining the best retention policy.

Ensure that the log/out files are removed from the below directory as you run "Purge Concurrent Request and/or Manager Data program":

$APPLCSF/$APPLLOG
$APPLCSF/$APPLOUT

See Doc ID 844976.1 for more details.

Need a Holistic view of your Concurrent Processing? Choose CP Analyzer v1.03

Concurrent Processor Analyzer sample output

Go to Doc ID 1411723.1 for more details and script download.

The Concurrent Processing Analyzer is a Self-Service Health-Check script which reviews the overall Concurrent Processing Footprint, analyzes the current configurations and settings for the environment providing feedback and recommendations on Best Practices.

This is a non-invasive script which provides recommended actions to be performed on the instance it was run on. For production instances, always apply any changes to a recent clone to ensure an expected outcome.

For top Concurrent Processing content, visit:

  • 11i / R12: Concurrent Processing - Product Information Center (PIC) Doc ID 1304305.1
Comments:

After running cp analyzer in my instance for PROD:

Total Purge Eligible Records in FND_CONCURRENT_REQUESTS I have seen this what does this indicates. Do we need truncate any tables or what

Posted by guest on February 25, 2015 at 01:07 PM EST #

Hello and thank you for the post. You should never truncate any tables unless directed to do so by support.

The Total Purge Eligible Records in FND_CONCURRENT_REQUESTS indicates that's the total number of records that can be purged on the instance. That can be controlled by regularly running the Purge Concurrent Request and/or Manager Data Program request. Below are some articles for the request:

Concurrent Processing - How to Optimize the Process of Running Purge Concurrent Request and/or Manager Data (FNDCPPUR)(Doc ID 92333.1)

Concurrent Processing - Purge Concurrent Request and/or Manager Data Program (FNDCPPUR)(Doc ID 104282.1)

The following MOS Community would be the ideal location to seek assistance on this as it's specific to feedback on the CP Analyzer:

https://community.oracle.com/thread/3093389

Thank you,
Brian

Posted by Brian Kerr on February 25, 2015 at 02:14 PM EST #

Thanks foe the reply.

I was not sure , when I ran cp analyzer in the red hilighted line it shows:

" Your overall Concurrent Processing HealthCheck Status is in need of Immediate Review!
The data in the FND_CONCURRENT_REQUESTS Table suggests request purging is never performed on a regular basis.
This Gauge is merely a simple indicator about volume of Concurrent Request data on P035.
It displays GREEN if less than 3,500 rows are found, ORANGE if less than 5,000, and RED if over 5,000 rows are found.
Clean up Concurrent Request Data and move the needle to green. "

I was not sure what exactly we need to figure out here

Posted by guest on February 25, 2015 at 03:35 PM EST #

I dont know about this, what to do here.

Your overall Concurrent Processing HealthCheck Status is in need of Immediate Review!
The data in the FND_CONCURRENT_REQUESTS Table suggests request purging is never performed on a regular basis.
This Gauge is merely a simple indicator about volume of Concurrent Request data on P590.
It displays GREEN if less than 3,500 rows are found, ORANGE if less than 5,000, and RED if over 5,000 rows are found.
Clean up Concurrent Request Data and move the needle to green.

Posted by guest on February 25, 2015 at 10:43 PM EST #

Thank you for the update.

From the first line of the output you provided:

Your overall Concurrent Processing HealthCheck Status is in need of Immediate Review!

That indicates that you have completed concurent requests that should be purged. This can be done by regularly running the Purge Concurrent Request and/or Manager Data Program request.

Please post any further questions / problems regarding this in the following community:

https://community.oracle.com/thread/3093389

Thank you,
Brian

Posted by Brian on February 26, 2015 at 08:34 AM EST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected

Twitter

Search

Archives
« July 2015
SunMonTueWedThuFriSat
   
4
5
10
11
12
13
14
15
17
18
19
22
24
25
26
27
28
29
30
31
 
       
Today