An Oracle tablespace ran out of space, but no alarms have been raised.
The DBO - Tablespace Used Percentage rule is enabled and the thresholds are set properly.
The Oracle agents are collecting Oracle metrics successfully and the IC agents (e.g. UnixAgentPlus, WindowsAgent, etc) are collecting successfully from the affected server as well.
Tablespace offline data collection only runs every 4 hours and did not capture this event. This is the default collection frequency in older versions of the Oracle Cartridge.
After an Oracle Cartridge upgrade a few DBO_Datafile objects may fail to upgrade correctly leaving an older version of the datafile object associated to the same parent tablespace object. This causes the DBO_allocated_space_used_pct_for_rules metric to estimate more room to grow than what actually exists. If so, this shows up on the Storage dashboard after selecting the affected Tablespace.
By default in older versions of the Oracle cartridge the offline tablespace data collection is set to 14400 seconds / 4 hours. If the issue happen between 2 collections and the DBA solved the issue before the next collection happen, the issue will not be captured.
To avoid such situations, change the collection interval to a appropriate time interval, for example one hour.
To do so, follow the steps below:
These duplicate objects can be removed from the Object Cleanup dashboard.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center