Excluding parameter alarms

The PATROL space parameters go into an alarm state when a tablespace or tablespace object is full. If a tablespace or object does not have available free space or extents, but the tablespace or object is not scheduled to receive anymore data, you can exclude it from being monitored by the space parameters.

The following table lists the tablespace or tablespace object conditions that cause the listed space parameters in the AVAILABILITY application to go into a warning or alarm state.
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

You can exclude the following types of objects:

• tables
• cluster
• index
• schemas
• partitions
• tablespaces (Locally Managed Tablespaces--UNIFORM extent size)
• temporary tablespaces (both Dictionary Managed Temporary Tablespaces and Locally Managed Temporary Tablespaces)

When you exclude an object in a tablespace, only that object is excluded from setting off parameter alarms.

• If you exclude a tablespace, all objects in that tablespace is not monitored by the space parameters.
• If you exclude an object in a tablespace, only that object is not monitored by the space parameters.
• If you exclude a schema, all objects that are owned by the user, wherever they are located in the instance, are not monitored by the space parameters.
• If you exclude a partition, only that partitioned part of the table is excluded. To exclude all of a partitioned table from being monitored, you must exclude all partitions that create that table.
• If you exclude a tablespace or tablespace object, PATROL still monitors the tablespace, but the space parameters do not go into alarm. However, the information about the tablespace or tablespace object still appears on relevant reports, and the tablespace is still monitored for file input and output.
• In a large environment, using space parameters such as FreeSpace, SpaceLeft, PctUsed, and so on affects the performance of BMC PATROL for Oracle.