Overview

Sentinel alert received says that UNDO_SPACE tablespace is almost full, although there is tablespace.

Additionally, it is known that this tablespace only needs to be monitored since it is auto-managed by ORACLE database engine for extension or release.

This alert is a concern because a filled or a non-auto-extensible tablespace can cause failures when new records are added.

Important Note: If you are unsure about securely performing the steps mentioned in this article, always make a backup before making any changes or reach out to support for more help.

Environment

Product: Prologic
Component: Server Environment Support

Requirement

Access to Database. 

Information

Since this is an auto-managed tablespace, there will be no record failures. However, it is recommended to check the current tablespace size with the following query:

select df.tablespace_name "Tablespace", totalusedspace "Used MB", (df.totalspace - tu.totalusedspace) "Free MB", df.totalspace "Total MB",
round(100 * ( (df.totalspace - tu.totalusedspace)/ df.totalspace)) "Pct. Free"
from
(
  select tablespace_name, round(sum(bytes) / 1048576) TotalSpace
  from dba_data_files
  group by tablespace_name
) df,
(
  select round(sum(bytes)/(1024*1024)) totalusedspace, tablespace_name
  from dba_segments
  group by tablespace_name
) tu
where df.tablespace_name = tu.tablespace_name 
AND df.tablespace_name = 'UNDO_SPACE' 
order by df.tablespace_name