"UNDO Tablespace full"
Marcio Almeida, August 15, 2012 - 2:30 pm UTC
Thank you for your support and time !
Undo tbs on 11g
A reader, August 16, 2012 - 7:53 pm UTC
The behavior for UNDO tablespaces have changed quite a bit from 11g onwards. We faced similar problems and that is what was told to us by Oracle Support. You might want to check is retention guarantee is enforced for the undo tbs.
It wasn't in our case but still we had the same problem as times.
Cheers.
Tony, February 14, 2014 - 3:42 pm UTC
Regarding the previous remarks, I was checking UNDO tablespace usage with a totally different statement, and I was getting what I thought was valuable data : often very low numbers, and occasionally high. Almost never hitting the actual maximum.
Given that is totally different from the initial question stating that UNDO is always "used completely", what exactly is different from this query then :
select round(USAGEMB)
from (select sum(bytes)/1024/1024/1024 SIZEMB, b.tablespace_name
from dba_data_files a, dba_tablespaces b
where a.tablespace_name = b.tablespace_name
and b.contents = 'UNDO'
and upper(b.tablespace_name)=upper('$undo_instance_1')
group by b.tablespace_name) a,
(select c.tablespace_name, sum(bytes)/1024/1024/1024 USAGEMB
from DBA_UNDO_EXTENTS c
where status <> 'EXPIRED'
and upper(c.tablespace_name)=upper('$undo_instance_1')
group by c.tablespace_name) b
where a.tablespace_name=b.tablespace_name
and upper(b.tablespace_name)=upper('$undo_instance_1');
Is this a correct way to measure UNDO usage, or is this attempt really not doing that ?