Page 1 of 3

Best Practices for Performance for Concurrent Managers in E-Business Suite [ID 1057802.1]

Modified 27-OCT-2010 Type BULLETIN

In this Document
Purpose
Scope and Application
Best Practices for Performance for Concurrent Managers in E-Business Suite
References

Applies to:
Oracle Application Object Library - Version: 11.5.0 to 12.1 - Release: 11.5.10 to 12
Information in this document applies to any platform.

Purpose
Provide the best practices to achieve better performance for concurrent manager in Oracle E-Business Suite.

Scope and Application

Applications DBAs, System Administrators involved in configuration and administration of Oracle E-Business Suite.

Best Practices for Performance for Concurrent Managers in E-Business Suite

Best Practices for Performance for Concurrent Managers in E-Business Suite

This Document contains 3 topics.

1. Generic Tips
2. Transaction Manager (TM)
3. Parallel Concurrent Processing (PCP) Environment

Generic Tips

1) Sleep Seconds - is the number of seconds your Concurrent manager waits between checking the list of pending concu

Setdocument
Tip:this
Rate the sleep time to be very brief during periods when the number of requests submitted is expected to b

2) Increase the cache size (number of requests cached) to at least twice the number of target processes.

For example, if a manager's work shift has 1 target process and a cache value of 3, it will read three requests, and try to

Tip: Enter a value of 1 when defining a manager that runs long, time-consuming jobs, and a value of 3 or 4 for managers

3) Create specialized concurrent managers to dedicate certain process either short or long running programs to avoid que

4) To maximize throughput consider reducing the sleep time of the Conflict Resolution Manager (CRM). The default value

5) Avoid enabling an excessive number of standard or specialized managers. It can degrade the performance due

6) Set the system profile option "Concurrent: Force Local Output File Mode" to "Yes" if required . You need to apply patch

Refer Note.822368.1: Purge Concurrent Request FNDCPPUR Does Not Delete Files From File System or Slow

Note:- The profile option "Concurrent: Force Local Output File Mode" is set to "No" by default. After applying the
enable this feature, All Concurrent Manager nodes must be able to access the output file location via the local filesystem

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULL... 9/11/2010
 Page 2 of 3

7) Truncate the reports.log file in log directory. Refer Note.844976.1 for more details

Truncation of file "reports.log" is a regular maintenance work of Application DBA. Make sure that reports log file
and regularly depending on number of concurrent program which uses "reports.log". You can safely truncate "reports.log"

8) Ensure "Purge Concurrent Request and/or Manager Data, FNDCPPUR," is run at regular intervals with "Entity" parame

9) Ensure that the log/out files are removed from the locations shown below as you run "Purge Concurrent Request

$APPLCSF/$APPLLOG
$APPLCSF/$APPLOUT

In the event that it does not remove the log/out files, over a period of time it will slow down the performance. Please refer

Note.822368.1: Purge Concurrent Request FNDCPPUR Does Not Delete Files From File System or Slow performance

10) Defragment the tables periodically to reclaim unused space / improve performance

FND_CONCURRENT_REQUESTS
FND_CONCURRENT_PROCESSES
FND_CRM_HISTORY
FND_ENV_CONTEXT
FND_TEMP_FILES

How to defragment

10.1) alter table <owner>.<table_name> move;

10.2) Note that, some indexes might become unusable after table is moved, check the index status from dba_
select owner, index_name, status from dba_indexes
where table_owner = upper('&OWNER') and
table_name = upper('&SEGMENT_NAME');

Note: Ensure the tablespace in which the object currently exists has got sufficient space before you move/def
before performing it on Production instance.

10.3) You will need to collect the statistics for the tables.

For example:
exec fnd_stats.gather_table_stats ('APPLSYS','FND_CONCURRENT_REQUESTS',PERCENT=>99);

Transaction Manager (TM)

11 ) Profile Concurrent:Wait for Available TM - Total time to wait for a TM before switchover to next available TM. Consi

12) Ensure enough TMs exist to service the incoming request load.

13) When the load is high, set the following profile to optimum values to achieve better results.

PO: Approval Timeout Value - Total time for workflow call (When initiated from Forms) to time out.

14) Set the sleep time on the Transaction Manager to a high number (e.g. 10 minutes), this avoids constant polls to chec

Parallel Concurrent Processing (PCP) Environment

15) If the failover of managers is taking too long refer to Note:551895.1: Failover Of Concurrent Manager Processes Take

16) Set profile option 'Concurrent: PCP Instance Check' to 'OFF' if instance-sensitive failover is not required. Setting

17) Transaction Manager uses DBMS_PIPE to communicate with application session prior to 11i.ATG_PF.H RUP3. DBM
Type' to ‘QUEUE'

Note Pipes are more efficient but require a Transaction Manager to be running on each DB Instance (RAC). So you

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULL... 9/11/2010
 Page 3 of 3

18) Add these parameters depends on your Database version

+ _lm_global_posts=TRUE
+ _immediate_commit_propagation=TRUE (11g RAC)
+ max_commit_propagation_delay=0 (9i RAC)

References
NOTE:551895.1 - Failover Of Concurrent Manager Processes Takes More than 30 Minutes
NOTE:822368.1 - Purge Concurrent Request FNDCPPUR Does Not Delete Files From File System or Slow performance
NOTE:844976.1 - All Concurrent Reports Are Failing With Error REP-0004,REP-0082 And REP-0104

Related

Products

• Oracle E-Business Suite > Applications Technology > Application Object Library > Oracle Application Object Librar

Keywords

RAC; FND_CONCURRENT_REQUESTS; FNDCPPUR; CONFLICT RESOLUTION; FAIL OVER; PARA

Back to top

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULL... 9/11/2010