Oracle Solutions We believe in delivering tangible results for our customers in a cost-effective manner
Purge Concurrent Request and Manager Data Program Concept and Effecting Tables
Overview
To maintain database performance and avoid excessive disk space usage, Oracle EBS provides the FNDCPPUR concurrent program (Purge Concurrent Request and/or Manager Data) for cleaning up historical concurrent request data, logs, and related information.
Key Tables Updated by FNDCPPUR Program
When the FNDCPPUR program runs, it updates or purges records from the following tables:
| Table Name | Description |
|---|---|
| FND_CONCURRENT_REQUESTS | Stores a complete history of all concurrent requests. Recommended to keep around 4,000–5,000 records. Should be purged regularly (every 30 days or so). |
| FND_RUN_REQUESTS | Contains information about report sets and parameter values for each report submitted. |
| FND_CONC_REQUEST_ARGUMENTS | Records arguments passed by the concurrent manager to each program it starts. |
| FND_DUAL | Tracks requests that do not update database tables. |
| FND_CONCURRENT_PROCESSES | Records information about Oracle Applications and operating system processes. |
| FND_CONC_STAT_LIST | Collects runtime performance statistics for concurrent requests. |
| FND_CONC_STAT_SUMMARY | Contains performance summary statistics generated by the purge process. |
| FND_ENV_CONTEXT | Stores information about environment names and values for each concurrent process. |
Additional tables that may be purged:
-
FND_FILE_TEMP
-
FND_CRM_HISTORY
-
FND_TM_EVENTS
-
FND_TEMP_FILES
-
FND_CONFLICTS_DOMAIN
-
FND_CONC_PP_ACTIONS
-
FND_RUN_REQ_PP_ACTIONS
Importance of Regular Purging
Regularly purging these tables and associated log/output files:
-
Prevents file system space issues.
-
Improves overall application performance.
-
Ensures optimal database response times.
Recommended Purge Schedule
-
Every 30 days — for normal system usage.
-
Every 14 days — for systems with heavy usage.
-
Daily (off-hours) — when using AGE mode with an appropriate value for recent data retention.
Program Options and Parameters
ENTITY Parameter
Determines which data is purged:
| Option | Description | Affected Tables / Files |
|---|---|---|
| ALL | Purges concurrent requests, managers, log files, and report output files. | – FND_CONCURRENT_PROCESSES – FND_DUAL – FND_CONCURRENT_REQUESTS – FND_RUN_REQUESTS – FND_CONC_REQUEST_ARGUMENTS – FND_ENV_CONTEXT – Deletes log and output files |
| MANAGER | Purges concurrent managers and their log files. | – FND_CONCURRENT_PROCESSES – FND_DUAL – Deletes manager log files |
| REQUEST | Purges concurrent requests, their log files, and output files. | – FND_CONCURRENT_REQUESTS – FND_RUN_REQUESTS – FND_CONC_REQUEST_ARGUMENTS – FND_DUAL – Deletes request log and output files |
Mode Parameter
Specifies the purging criteria:
-
AGE: Retains data for the number of days specified.
-
COUNT: Retains a specific number of records.
Valid Mode Values: 1 - 9999999
Reference: Concurrent Processing – Purge Concurrent Request and/or Manager Data Program (FNDCPPUR) (Doc ID 104282.1)
