Scribd
Upload
31 views2 pages

Purging Request

This document outlines several Oracle Data Purging Requests including: purging ATP temp tables, concurrent request and manager data, diagnostic and log messages in 11i, FND_STATS history records, logs and closed alerts in r12, obsolete generic file manager data, obsolete SOA monitor data, obsolete workflow runtime data, rule executions, and signon audit data. The requests aim to periodically purge temporary, obsolete, or historical data from Oracle applications to manage database size.

Uploaded by

Amir Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
31 views2 pages

Purging Request

This document outlines several Oracle Data Purging Requests including: purging ATP temp tables, concurrent request and manager data, diagnostic and log messages in 11i, FND_STATS history records, logs and closed alerts in r12, obsolete generic file manager data, obsolete SOA monitor data, obsolete workflow runtime data, rule executions, and signon audit data. The requests aim to periodically purge temporary, obsolete, or historical data from Oracle applications to manage database size.

Uploaded by

Amir Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Oracle Data Purging Request

 Purge ATP Temp Tables:


Oracle Inventory uses the item or organization ATP(Available to promise) rule to
determine the supply and demand to be considered in the calculation.
Attention: ATP Inquiry is for informational purposes only and does not place
demand or reserve on-hand inventory.
 Purge Concurrent Request and/or Manager Data:
This program is use to delete:

o request log files, concurrent manager log files, and report output files from
your product directories maintained by the operating system

o records (rows) from Application Object Library database tables that


contain history information about concurrent requests and concurrent
manager processes.

 Purge Diagnostic and Log Messages in 11i:


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).
 Purge FND_STATS History Records:
This program can be run to purge the history records from the FND_STATS_HIST
table. This program should be scheduled to run periodically if statistics are being
gathered with History Mode as FULL. You do not need to run this program if you
gather statistics with History Mode as NONE or the default – LASTRUN.

 Purge Logs and Closed System Alerts in r12:


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).
 Purge Obsolete Generic File Manager Data:
The request is used to purge uploaded files from the Generic File Manager. Some
of the data that gets into this table belongs to old/expired exports. For every
request for an export, an entry in the FND_LOBS table is recorded. This data must
be purged regularly. The report is based on a PL/SQL procedure, which gets rid of
old obsolete uploaded files (loaded to the database) for the programs FND_HELP,
export and FND_ATTACH, these are programs that are run under the FNDGFU
(Generic File Manager Access Utility).

 Purge Obsolete SOA Monitor Data:


SOA Monitor is a centralized, light-weight service execution monitoring and
management tool. It not only monitors all the web service activities that SOA
Provider and Web Service Provider process, but also provides auditing records for
the service execution details if the auditing feature is enabled.
Oracle E-Business Suite Integrated SOA Gateway allows you to purge SOAP
messages, logs, and audit records that have been collected through SOA Monitor
for a period of time.

 Purge Obsolete Workflow Runtime Data:


By default, this program purges obsolete runtime information associated with
work items as well as obsolete design information, such as activities that are no
longer in use and expired users and roles, and obsolete runtime information not
associated with work items, such as notifications or Oracle XML Gateway
transactions that were not handled through a workflow process.

 Purge Rule Executions:

 Purge Signon Audit data:


Purges all Signon Audit information created before a given date.

 Purge Web Service Audit Data:

You might also like