| < Day Day Up > |
|
You can control how long and how many log and output files to retain at the OS level. Once you have made the determination how long to retain these files, the Purge Concurrent Request Concurrent Program or the Manager Data Concurrent Program will act, based on the information located in the database tables found in Table 12.5 to determine which files it can safely purge and which it needs to retain. Table 12.6 provides a detailed list of parameters accepted by the report. The retention policy for these log and output files needs to be determined by your Applications users. Archiving policy needs to be determined by the corporate IT departments. These policies can then be implemented, in part, through these concurrent requests.
Table Name | Description |
---|---|
FND_CONCURRENT_REQUESTS | Contains a complete history of all concurrent requests (both past history and those scheduled to run in the future). |
FND_RUN_REQUESTS | Stores information about the reports in a report set that a user submits including the report set's parameter values. |
FND_CONC_REQUEST_ARGUMENTS | Records all arguments passed by Concurrent Managers to concurrent requests as those requests are running. |
FND_DUAL | Records when a request does not update any database tables. |
FND_CONCURRENT_PROCESSES | Records information about Oracle Applications processes and OS processes. |
FND_CONC_STAT_LIST | Collects runtime performance statistics for concurrent requests. |
FND_CONC_STAT_SUMMARY | Contains Concurrent Program performance statistics generated by the Purge Concurrent Request program or the manager data program. These programs use the data in FND_CONC_STAT_LIST to compute these statistics. |
Report Option | Granularity | Meaning |
---|---|---|
Entity | All | Purges records from database history tables for requests and concurrent requests. Purges log files, manager log files, and output files from OS. |
Manager | Retains information on reports and purges information on manager from history table and log file from server. | |
Request | Retains information on Concurrent Manager. Purges information on concurrent requests from tables, log files, and out files from the OS. | |
Mode | Age | Number of days you want to retain request history table records and log and output files. |
Count | Number of most recent records of concurrent history to retain. | |
Mode Value | Value to define the age or count number for mode. Valid values are 1 to 9999999. | |
Oracle ID | The Oracle ID of the concurrent request submitter for whom you want to purge concurrent request records, log files, and output files. Relevant only if entity is "All" or "Request." | |
Username | Application username to whom the concurrent requests to be purged belong. Simpler to use than Oracle ID as Username is easier to determine. Relevant only if entity is "All" or "Request." | |
Responsibility | Responsibility for whom you want to purge concurrent information. Example: System Administrator Relevant only if entity is "All" or "Request." | |
Program Application | Application for which you want to purge concurrent information. Example: Oracle Receivables Relevant only if entity is "All" or "Request." | |
Program | Concurrent Program for which you want to purge concurrent information. Relevant only if entity is "All" or "Request." | |
Manager Application | Application associated to Concurrent Manger for which you want to purge concurrent information. Used with Manager option. Entity = Request, all requests associated with those run by Concurrent Manager named in the Manager option. Entity = Manager or All, purges all of those purged by "Entity = Request" and also those manager log files associated with that manager. | |
Manager | Concurrent Manager for whom you want to purge concurrent information. Same entity rules as for Manager Application. | |
Report | Yes | Generate report listing number of records purged. |
No | Run program, do not generate report. | |
Purge Other | Yes | Delete records from FND_DUAL. |
No | Do not delete records from FND_DUAL. |
You can maintain statistics on concurrent requests, even after they have been purged from the system, by setting the Concurrent: Collect Request Statistics profile option to yes. These statistics can help you determine where best to start tuning long running or time-intensive concurrent requests.
| < Day Day Up > |
|