Concepts concurrent Programs Purge    



Tables involved in concurrent requests

FND_CONCURRENT_REQUESTS		 This table contains a complete history of all concurrent requests. Use FNDCPPUR to purge it. Keep only about 30 days worth of data to not affect performance. The amount of data to keep is a business decision. Verify with the business own how much data to keep, or that you can purge.
FND_RUN_REQUESTS

This table stores information about submitted 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  
   
   
Concurrent Purge Notes

ID 419990.1 Table Fnd_env_context Growing Very Fast

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

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

ID 1335304.1 FNDCPPUR Request Does Not Always Delete Files From The File System, Many Files Will Be Denoted As "deletion failed" 

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












Notes from the Oracle® Applications
Concepts
Release 12.1

Types of Concurrent Manager
The Internal Concurrent Manager (ICM) controls all other concurrent managers. It administers the startup and shutdown of managers as defined by their work shift, monitors for process failure, and cleans up if a failure occurs. The ICM does not processes concurrent requests itself (except for queue control requests, such as ACTIVATE, DEACTIVATE, or ABORT).
The Conflict Resolution Manager (CRM) enforces rules designed to ensure that
incompatible concurrent requests do not run in the same conflict domain(an abstract representation of the groupings used to partition data).
The Standard Manage will accept and run any concurrent requests, as it has no specialization rules that would restrict its activities
Transaction Managers support synchronous request processing, whereby a pool of server
processes responds to requests from client programs. Instead of polling the concurrent requests table to obtain instructions, a transaction manager waits to be signaled by a client. An example is approval of an order, where execution of the request must take place quickly.