V$UNDOSTATdisplays a histogram of statisticaldatato show how well the system is working. The available statistics include undo space consumption, transaction concurrency, and length of queries executed in the instance. You can use this view to estimate the amount of undo space required for the current workload.Oracleuses this view to tune undo usage in the system. The view returns null values if the system is in manual undo management mode.
Each row in the view keeps statistics collected in the instance for a 10-minute interval. The rows are in descending order by theBEGIN_TIMEcolumn value. Each row belongs to the time interval marked by (BEGIN_TIME,END_TIME). Each column represents the data collected for the particular statistic in that time interval. The first row of the view contains statistics for the (partial) current time period. The view contains a total of 1008 rows, spanning a 7 day cycle.
Represents the last active undo tablespace in the duration of time. The tablespace ID of the active undo tablespace is returned in this column. If more than one undo tablespace was active in that period, the active undo tablespace that was active at the end of the period is reported.
Represents the total number of undo blocks consumed. You can use this column to obtain the consumption rate of undo blocks, and thereby estimate the size of the undo tablespace needed to handle the workload on your system.
Identifies the total number of transactions executed within the period
Identifies the length of the longest query (in seconds) executed in the instance during the period. You can use this statistic to estimate the proper setting of theUNDO_RETENTIONinitialization parameter. The length of a query is measured from the cursor open time to the last fetch/execute time of the cursor. Only the length of those cursors that have been fetched/executed during the period are reflected in the view.
Identifies the number of times the errorORA-01555occurred. You can use this statistic to decide whether or not theUNDO_RETENTIONinitialization parameter is set properly given the size of the undo tablespace. Increasing the value ofUNDO_RETENTIONcan reduce the occurrence of this error.
Identifies the number of times space was requested in the undo tablespace and there was no free space available. That is, all of the space in the undo tablespace was in use by active transactions. The corrective action is to add more space to the undo tablespace.
Total number of blocks in the active extents of the undo tablespace for the instance at the sampled time in the period
Total number of blocks in the unexpired extents of the undo tablespace for the instance at the sampled time in the period
Total number of blocks in the expired extents of the undo tablespace for the instance at the sampled time in the period