Cannot Auto Extend (CannotExtend)


Warning

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.

Displays whether a segment in an autoextensible tablespace cannot extend due to a lack of operating system space or reaching the maximum space on the tablespace.

This parameter monitors only autoextensible tablespaces and tablespaces with an allocation type UNIFORM. If a non-autoextensible tablespace cannot extend, the Free Space Deficit (FreeSpaceDeficit) parameter goes into alarm. 

Only permanent tablespaces are monitored by this parameter. To monitor temporary tablespaces, you must use Smallest Free Space Available in Temporary Tablespaces (TempTSLeft) and Smallest Free Space % Available in Temporary Tablespaces (TempTSLeftPct).

We use the following pconfig variable to set the minimum size left until we consider the tablespace cannot be extend.

/OracleConfig.{sid}.cannotExtMaxFreeBytes

If this parameter is not set the default value is 1024*1024, which equals 1MB.

Recommendations

The parameter alerts only if there is no space available for the tablespace to allocate the next extent. In order to get a proactive monitoring notification and alerts before an ORA error occurs, see ETSM (ORACLE_ETSM).

If the tablespace can no longer extend due to a lack of operating system space, delete or move error log files, archive files, or any unnecessary files.

If the tablespace can no longer extend due to reaching the maximum space in the tablespace, increase the space in the tablespace.

Note

This parameter is also supported if the instance uses ASM storage.

In case of an Instance that uses ASM storage, the ORACLE_AVAILABILITY application class uses V$ASM_DISKGROUP_STAT view to get the free space for disk groups those are used for storing the data files. The free space is considered only for the disk groups those are in mounted /connected state when the query is performed from the monitored instance.

Warning

 Do not adjust the alarm ranges for this parameter. If you want to suppress alarms and warnings, disable Border Alarm, Alarm1 and Alarm2. This allows the parameter to continue gathering data without going into an alert state. If you want to stop the parameter from gathering data, deactivate the parameter.  

BMC PATROL properties

Attribute

Default value

Application class

ORACLE_AVAILABILITY

Command type

not applicable

Platform

all

Icon style

Boolean

Unit

none

Border range

undefined

Alarm1 range

1-1 alarm

Alarm2 range

undefined

Scheduling(poll time)

poll time of collector

Active at installation

Yes

Parameter type

Consumer

Value set by

CollAvailability

BMC ProactiveNet Performance Management properties

Property

Default value

Monitor type

Oracle Database Availability

Key Performance IndicatorYes
Monitor for abnormalities
Yes
Graph by default
No
AvailabilityNo
Response time
No
Normal distribution
Yes
StatisticalNo
Was this page helpful? Yes No Submitting... Thank you

Comments