This chapter describes the precoded alerts that are included in your Oracle Alert installation.
This chapter covers the following topics:
Your Oracle Alert installation contains predefined alerts that are designed to help you manage your database and the data you generate when you use Oracle Alert. Oracle Alert provides eight alerts that systematically monitor your system for potential tablespace, disk space, and allocation problems, making your Database Administrators more efficient, and increasing database performance.
Occasionally, you will want to purge your database of obsolete concurrent requests, alert checks, and action set checks. Oracle Alert provides two alerts that let you periodically remove old files, freeing up valuable tablespace and increasing database performance.
All the precoded alerts are periodic alerts, so you determine how often they run. Set them to run daily, weekly, or monthly, according to your needs.
You can use inputs to customize your precoded alerts. You can also define your input values at the action set level, so you can create multiple action sets that target different input values. You can create as many action sets as you need.
This section gives you an overview of these alerts, and suggestions on how to use them to enhance your system performance.
Related Topics
Oracle Alert Database Administration (DBA) alerts help you manage your database by notifying you regularly of:
Tables and indexes unable to allocate another extent
Users who are nearing their tablespace quota
Tablespaces without adequate free space
Tables and indexes that are too large or are fragmented
Tables and indexes that are near their maximum extents
If Oracle Alert finds the database exceptions specified in a DBA alert, it sends you a message summarizing all exceptions found. If Oracle Alert finds no exceptions, it sends you a message reporting that no exceptions were found. Oracle Alert keeps you notified of the status of your database, even if it is unchanging.
The Applications DBA application owns the Oracle Alert DBA alerts. This lets Oracle Alert perform the DBA alerts for every database instance you create, even those that reside outside Oracle Alert's database.
The following descriptions list the customizable frequency and inputs of each DBA alert.
This alert looks for tables where the next extent is larger than the largest free extent.
Frequency: Every N Calendar Days
Inputs:
Table Name
Oracle Username
This alert looks for indexes where the next extent is larger than the largest free extent.
Frequency: Every N Calendar Days
Inputs:
Index Name
Oracle Username
This alert detects users that are near their tablespace quota.
Frequency: Every N Calendar Days
Inputs:
Oracle Username
Tablespace Name
Check minimum percent free space remaining
Check maximum percent space used
Minimum free space remaining (in bytes)
Maximum percent space used
This alert looks for tablespaces without a specified minimum amount of free space.
Frequency: Every N Calendar Days
Inputs:
Tablespace Name
Check total free space remaining
Check maximum size of free extents available
Maximum size of free extents available (in bytes)
Minimum total free space remaining (in bytes)
This alert detects indexes that exceed a specified number of blocks or extents.
Frequenc: Every N Calendar Days
Inputs:
Index Name
Oracle Username
Check maximum number of blocks
Check maximum number of extents
Maximum number of blocks
Maximum number of extents
This alert detects tables that exceed a specified number of blocks or extents.
Frequency: Every N Calendar Days
Inputs:
Table Name
Oracle Username
Check maximum number of blocks
Check maximum number of extents
Maximum number of blocks
Maximum number of extents
This alert searches for tables and indexes that are within a specified number of extents of their maximum extents.
Frequency: Every N Calendar Days
Inputs:
Table Name
Oracle Username
Minimum number of extents remaining
This alert searches for tables and indexes that are within a specified number of extents of their maximum extents.
Frequency: Every N Calendar Days
Inputs:
Index Name
Oracle Username
Minimum number of extents remaining
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:
Automatically delete concurrent requests older than a specified number of days
Automatically clean out alert checks and action set checks that are older than a specified number of days
The following descriptions list the customizable frequency and inputs of each purging alert.
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, Oracle E-Business Suite System Administrator's Guide - Maintenance.
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.