------This article explains the functions of the tables under the concurrent manager w ith simple guidelines for

the Purge Concurrent Request and/or Manager Data Program, FNDCPPUR, which affects them. Tables that are updated when Oracle Applications Concurrent Program is started ------------------------------------------------------------------------------, FND_CONCURRENT_REQUESTS t at around 4 - 5k records and should be regularly purged as part of normal 'housekeeping' by running the standard FNDCPPUR progr am. This is a part of basic system administration and it is recommended that for the average instance, it should be run every 30 days or so. Allowing the table ( and others ) to increase in size can affect performance. 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. This table contains a complete history of all concurrent requests. This table should ideally be kep

FND_CONC_REQUEST_ARGUMENTS This table records arguments passed by the concurrent manager to each program it starts running. FND_DUAL FND_CONCURRENT_PROCESSES FND_CONC_STAT_LIST FND_CONC_STAT_SUMMARY FND_ENV_CONTEXT This table records when requests do not update database tables. This table records information about Oracle Applications and operating system processes. This table collects runtime performance statistics for concurrent requests. This table contains the concurrent program performance statistics generated by the Purge. This table stores information about environment name and value for each of the concurrent process

To avoid running out of space on your disk drives, you should periodically delete Oracle Applications log files, output files and purge these tables with the FNDCPPUR program. The FNDCPUR purge program maintains the number of log and output files the operating system retains, and manage tables that store information about concurrent requests and concurrent manager processes. You can run the program FNDCPPUR once and automatically resubmit the program for your specific time intervals. Here are some sample guidelines to run the purge program.

Adopt these guidelines according to your user community's usage of Oracle Applications. - every 30 days for normal usage - every two weeks (14 days) for heavy usage - if you are using the AGE mode, set the Mode Value to 7 or higher to retain the most recent days of concurrent request data, log files, and report output files. WARNING : When you purge concurrent request information, you lose audit details which are used by the Signon Audit Concurrent Requests report. FNDCPPUR Program options : ENTITY = ALL log files, : Purge of concurrent requests, concurrent managers, request manager log files and report output files. The following tables are purged - Fnd_Concurrent_Processes - Fnd_Dual - Fnd_Concurrent_Requests, - Fnd_Run_Requests - Fnd_Conc_Request_Arguments - Fnd_Dual - Fnd_Context_Env - Deletes concurrent requests' log and out files from OS ENTITY = MANAGER : Purge of concurrent managers and manager log files. The following tables are purged - Fnd_Concurrent_Processes - Fnd_Dual - Deletes concurrent manager log files from OS ENTITY = REQUEST files. : Purge of concurrent requests, request log files and output The following tables are purged - Fnd_Concurrent_Requests, - Fnd_Run_Requests - Fnd_Conc_Request_Arguments - Fnd_Dual - Deletes concurrent requests' log and out files from OS Mode Mode Value User Name Oracle ID Program Application Program Manager Application Manager Resp. Application Responsibility : : : : : : : : : : AGE Number of days. COUNT Nuber of records valid values are 1 - 9999999 application username Oracle ID application program application associated with the concurrent manager concurrent manager application associated with the responsibility responsibility or "All".

Report

No Yes

Run the program but do not generate a report. Run the program and generate a report.

WARNING : The only option which purges all tables is the option "ENTITY = ALL". It is better to use this option to synchronise the Concurrent Requests and Concurrent Processes tables.. Related Documents ----------------For more parameter details, see Oracle Applications System Administrator's Guide