Previous  Next          Contents  Index  Navigation  Glossary  Library

Oracle Alert Purging Alerts

Two of the Oracle Alert precoded alerts are designed to help you manage the data you generate when you use Oracle Alert. While using Oracle Alert you should be able to:

The following descriptions list the customizable frequency and inputs of each purging alert.

Purge Concurrent Requests

This alert looks for concurrent requests and their log and out files that are older than the number of days you specify, and runs a concurrent program that deletes them. If you enter a concurrent program name input, you should use the program name (located in the column USER_CONCURRENT_PROGRAM_NAME in the table FND_CONCURRENT_REQUESTS), and not the optional description that may accompany the concurrent program name in the Concurrent Requests form.

Alert Type Periodic
Periodicity Every N Calendar Days
Inputs Application Name
Concurrent Program Name
Number of days since concurrent request was submitted to the concurrent manager
Operating System Program Deletes log file, out file, and corresponding record of each concurrent request
Arguments Concurrent request ID

Note: This precoded alert uses the concurrent program called Purge Concurrent Request and/or Manager Data Program as its action. See: Purge Concurrent Request and/or Manager Data Program.

Purge Alert and Action Set Checks

This alert looks for alert and action set checks older than the number of days you specify, and runs a SQL statement script that deletes them.

Alert Type Periodic
Periodicity Every N Calendar Days
Inputs Application Name
Number of days since alert check

Note: Oracle Alert will not delete alert checks and/or action set checks for a response processing alert that has open responses. See: Defining a Response Processing Alert.

         Previous  Next          Contents  Index  Navigation  Glossary  Library