From Using Join

From On JOin

Active: they are needed for Rollback, UNDO_RETENTION setting is not used here,
NOSPACEERRCNT column in V$UNDOSTAT
You will get ORA-30036 unable to extend segment in Undo tablespace errors
when no more space is left to store ACTIVE Undo.
This will automatically rollback the transaction causing it.
The NOSPACEERRCNT column in V$UNDOSTAT is a good indication how many times
this has occurred.

: Active undo is used by active transactions: rollback and read consistency,

update query running.

Expired: Data in these extends is committed, the UNDO_RETENTION time has passed,
not needed for Read Consistency.
: Expired undo is old and can be reused.

unexpired: transactions belonging to these undo extents are committed, Unexpired

extents are non-active extents that still honour UNDO_RETENTION, still want/need
these for Read Consistency!

: Unexpired undo is used for read consistency, retention time has not
passed yet.

: Unexpired undo can be stolen for Active undo. If this is happening you
can get ORA-01555 before Undo retention has passed.

: Unexpired undo can be secured by setting the RETENTION GUARANTEE option

when creating the Undo tablespace (see Undo Sizing).

Active extents stealing from unexpired extents, when no expired extents left for
reuse.

ORA-01555 snapshot too old errors if no Read Consistency information for a query
is available.
The SSOLDERRCNT in V$UNDOSTAT will show a count of these errors.

When the Undo mechanism requires more extents for ACTIVE extents, it is allowed to
steal UNEXPIRED extents when there are no EXPIRED extents left for reuse and it can
not allocate more free extents (autoextend maxsize reached or fixed tablespace
size). One can check the steal-count in UNXPSTEALCNT in V$UNDOSTAT

Flashback features using Undo are:

==================================
QTVTDD
=======

Flashback Query (based on time)

Flashback Versions Query (based on SCN)
Flashback Transaction Query (based on period)
Flashback Table (based on time)

Flashback Drop and Flashback Database do not use Undo information. Flashback Drop
is using not yet recycled segment and extents and Flashback Database is a
separate mechanism using the Flash/Fast Recovery Area, by taking snapshots and
redo information.

72
===