Incorrect Tablespace Alerts Generated for BYTES_FREE Metric. (Doc ID 1676260.1)

Last updated on MAY 27, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.2 and later
Information in this document applies to any platform.

Symptoms

 

Incorrect tablespace alerts are generated for BYTES_FREE metric in dba_outstanding_alerts. Sometime, Warning or Critical alerts are generated for Free tablespace. Sometimes, Critical alerts are generated instead of warning etc.

Create a new tablespace:

The alert is raised eventhough the tablespace is empty.

 

Another scenario will be:

Tablespace Bytes Space Usage LE 8192 LE 5120
=> warning less then 8Mb critical less then 5Mb .

But the alert raised is:

REASON
------------------------------------------------------------------------------
--
METRIC_VALUE MESSAGE_TYPE MESSAGE_LEVEL
------------ ------------ -------------
CREATION_TIME
---------------------------------------------------------------------------
Tablespace [TC] only has [7 megabytes] free space
7 Warning 1
05-FEB-13 07.39.05.857954 AM -08:00

=> ie, a critical alert is raised while 1st a warning should be raised for less then 8Mb. 

Or in other words, a warning alert is skipped and critical alert is raised for tablespace.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms