Monday, January 25, 2016

Oracle E-Business suite Purge Concurrent Programs

Purge Concurrent Request and/or Manager Data

System Administrator — Concurrent – Requests
Click on Submit a New Request — Select Single Request click ok
Enter Name as Purge Concurrent Request and/or Manager Data
Entity – ALL / Request / Manager
ALL – Purges records from database tables that record history information for concurrent requests,concurrent managers, and purges request log files, manager log files, and report output files from the operating system.
Request – Purges records from database tables that record history information for concurrent requests, and purges request log files and report output files from the operating system.
Manager – Purges records from database tables that record history information for concurrent managers, and purges manager log files from the operating system.
Mode – Age / Count
Age – Enter the number of days for which you want to save concurrent request history, log files, and report output files. The purge program deletes all records older (in days) than the number you enter. For example, if you enter “5”, then all concurrent request history, log files, and report output files older than five days is purged.
Count – Enter the number of (most recent) records for which you want to save concurrent request history, log file, and report output files. The purge program starts from the most recent records, retains the number you enter, and purges all remaining records. For example, if you enter “5”, then the five most recent concurrent request history records, request log files, manager log files, report output files are saved, and all remaining records are purged.

Mode Value – Value
Mode Value – Enter a value to define the number of days for Mode=Age or the number of records for Mode=Count. The valid values are 1 – 9999999
Then Submit.
The database tables that are affected by running the Purge Concurrent Request and/or Manager Data program are:
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_ARGUMENTSThis 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_PROCESSESThis 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_SUMMARYThis 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.

  Purge Sign on Audit data

The purge program takes action on below tables.

Select count(*) from fnd_logins;Select (*) from fnd_login_responsibilities;Select count(*) from fnd_login_resp_forms;Select count(*) from fnd_unsuccessful_logins;Select count(*) from fnd_appl_sessions;
Purge Logs and Closed System Alerts

Concurrent program “Purge Debug Log and System Alerts” in Release 11i and “Purge Logs and Closed System Alerts” in Release 12 is recommended way to purge messages. This program purges all messages up to the specified date,except messages for active transactions (new or open alerts, active ICX sessions, concurrent requests, and so on). This program is by default scheduled to run daily and purge messages older than 7 days. Internally this concurrent program invokes FND_LOG_ADMIN APIs.
Data from the following tables will be deleted when you run “Purge Logs and Closed System Alerts'” or “Purge Debug Log and System Alerts” program
FND_EXCEPTION_NOTES;
FND_OAM_BIZEX_SENT_NOTIF;
FND_LOG_METRICS;
FND_LOG_UNIQUE_EXCEPTIONS;
FND_LOG_EXCEPTIONS;
FND_LOG_MESSAGES;
FND_LOG_TRANSACTION_CONTEXT;
FND_LOG_ATTACHMENTS

No comments:

Post a Comment