Free Space Deficit (FreeSpaceDeficit)
This feature is no longer supported by the KM version 9.7.11.03. For more information see, 9.7.11.03: Fix Pack 3 for BMC PATROL for Oracle Database.
FreeSpaceDeficit parameter is a Boolean value that indicates whether there is at least one segment that cannot allocate its next extent because of insufficient space.
This parameter monitors all non-excluded dictionary-managed or locally-managed, uniform or system allocated, non-autoextensible tablespaces.
There is no mechanism to prevent the
FreeSpaceDeficit parameter from going into an alarm state where the
FreeSpace parameter is in an alarm state or warning state. However, the
FreeSpaceDeficit parameter does not go into an alarm state where there are no rows in
DBA_FREE_SPACE . The
FreeSpace parameter goes into an alarm state with 0% free space and there is no need for the
FreeSpaceDeficit parameter to go into an alarm state.
A segment is a set of database blocks allocated for storage of some database object. There are several types of segments, but all have a similar structure and are made up of extents. Segments start life with a specified number of extents and grow dynamically as extents are added when required.
If a tablespace is autoextensible, FreeSpaceDeficit does not go into an alarm state for that tablespace. If all monitored tablespaces are autoextensible, Cannot Auto Extend (CannotExtend) monitors autoextended tablespaces and their segments.
When this parameter alarms, the annotation reports all segments with insufficient available space.
This parameter considers tablespace, user, and object exclusions in its calculations for warnings and alarms.
Only permanent tablespaces are monitored by this parameter. To monitor temporary tablespaces, you must useSmallest Free Space Available in Temporary Tablespaces (TempTSLeft) and Smallest Free Space % Available in Temporary Tablespaces (TempTSLeftPct).
- This parameter gets de-activated only if all the tablespaces in the database are autoextensible.
- If the query for this parameter gives performance issues, you can skip the execution of this query by setting the value of the following pconfig variable to 1:
FreeSpaceDeficitquery will be skipped if the time taken to exceute the DBA_FREE_SPACE view is more than one minute.
- Under this scenario, the PATROL for Oracle Database generates an event with the following annotation report:
Instance: InstanceName; FreeSpaceDeficit = 1; parameter status = WARN
Time taken to execute select count(1) from dba_free_space is TimeTakenInMinutes minutes
FreeSpaceDeficit will not be executed if the execution time of "select count(1) from dba_free_space" is greater than 1 minute.
The possible cause may be due to the large number of entries in the sys.recyclebin$ that may need to be purged.
The product will execute the query only after the time taken to execute the DBA_FREE_SPACE view becomes less than one minute.
To avoid running out of space, perform one of the following tasks:
- Add a datafile to the affected tablespace.
- Change the storage parameters on the segments.
When you add a datafile to your tablespace, the datafile is not monitored until CollAvailability completes ten polling cycles.
Do not adjust the alarm ranges for this parameter. This parameter only responds to a setting of 0 or 1. If you want to suppress alarms and warnings, disable Alarm2 (Alarm1 is inactive by default), which allows the parameter to continue gathering the information without going into an alert state. If you want to stop the parameter from gathering information, deactivate the parameter.
BMC PATROL properties
Inactive by default
Poll time of collector
Active at installation
Value set by
BMC ProactiveNet Performance Management properties
Oracle Database Availability
|Key Performance Indicator||No|
|Monitor for abnormalities||Yes|
|Graph by default||No|