Purge Concurrent Request:
===========================
How to Run the Purge Concurrent Request and/or Manager Data Program and Which Tables Does it Purge?
To run the Purge Concurrent Request and/or Manager Data program:
1. Log in to Application as System Administrator responsibility.
2. Navigate to Request> Run> Single Request
3. Query up Purge Concurrent Requests.
4. For values to be entered in the parameter screen refer to the Oracle
Administration System Administration Guide
.
The following tables will be purged:
FND_CONCURRENT_REQUESTS
This table contains a complete history of all concurrent requests.
.
FND_RUN_REQUESTS
When a user submits a report set, this table stores information about the
reports in the report set and the parameter values for each report.
.
FND_CONC_REQUEST_ARGUMENTS
This table records arguments passed by the concurrent manager to each program
it starts running.
.
FND_DUAL
This table records when requests do not update database tables.
.
FND_CONCURRENT_PROCESSES
This table records information about Oracle Applications and operating system
processes.
.
FND_CONC_STAT_LIST
This table collects runtime performance statistics for concurrent requests.
.
FND_CONC_STAT_SUMMARY
This table contains the concurrent program performance statistics generated by
the Purge Concurrent Request and/or Manager Data program. The Purge Concurrent
Request and/or Manager Data program uses the data in FND_CONC_STAT_LIST to
compute these statistics.
FND_CONC_PP_ACTIONS
Stores the post request processing actions(e.g., print, notify) for each
submitted request. There’s a concurrent_request_id here for each request_id
in the FND_CONCURRENT_REQUESTS.
FND_RUN_REQ_PP_ACTIONS
Stores the post request processing actions(e.g., print, notify) for
submitted request set programs that are stored in FND_RUN_REQUESTS
FND_ENV_CONTEXT
This table stores information about environment name and value for each of the
How to Run the Purge Concurrent Request and/or Manager Data Program and Which Tables Does it Purge? To run the Purge Concurrent Request and/or Manager Data program:
Generic Tips
1) Sleep Seconds - is the number of seconds your Concurrent manager waits between checking the list of pending concurrent requests (concurrent requests waiting to be started).
2) Increase the cache size (number of requests cached) to at least twice the number of target processes.
3) Create specialized concurrent managers to dedicate certain process either short or long running programs to avoid queue length.
4) To maximize throughput consider reducing the sleep time of the Conflict Resolution Manager (CRM). The default value is 60 seconds. You can consider setting to 5 or 10 seconds.
5) Avoid enabling an excessive number of standard or specialized managers.
1) Sleep Seconds - is the number of seconds your Concurrent manager waits between checking the list of pending concurrent requests (concurrent requests waiting to be started).
2) Increase the cache size (number of requests cached) to at least twice the number of target processes.
3) Create specialized concurrent managers to dedicate certain process either short or long running programs to avoid queue length.
4) To maximize throughput consider reducing the sleep time of the Conflict Resolution Manager (CRM). The default value is 60 seconds. You can consider setting to 5 or 10 seconds.
5) Avoid enabling an excessive number of standard or specialized managers.
6) Set the system profile option “Concurrent: Force Local Output File Mode” to “Yes” if required .
7) Truncate the reports.log file in log directory.
7) Truncate the reports.log file in log directory.
8) Ensure “Purge Concurrent Request and/or Manager Data, FNDCPPUR,” is run at regular intervals with “Entity” parameter as “ALL”.
9) Ensure that the log/out files are removed from the locations shown below as you run “Purge Concurrent Request and/or Manager Data program”.
$APPLCSF/$APPLLOG
$APPLCSF/$APPLOUT
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
$APPLCSF/$APPLLOG
$APPLCSF/$APPLOUT
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
11 ) Profile Concurrent:Wait for Available TM - Total time to wait for a TM before switchover to next available TM. Consider setting this to 1 (second).
12) 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.
13) Set the sleep time on the Transaction Manager to a high number (e.g. 10 minutes), this avoids constant polls to check for shutdown requests.
12) 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.
13) Set the sleep time on the Transaction Manager to a high number (e.g. 10 minutes), this avoids constant polls to check for shutdown requests.
No comments:
Post a Comment