UNDO SEGMENT SPACE 中extent被使用的规则！

When a transaction needs more space in an undo segment, there is a fixed algorithm the determines when extents are reused.. The transaction will first attempt to reclaim expired extents from the current segment, then expired extents from another segment. The third method will be to autoextend the datafile(s), if this is set. Next, the unexpired extents from the current segment and other segments will be allocated, as long as the extents do not contain uncommitted transactions. Finally, an error will be raised if none of the methods are successful[@more@]

When a transaction needs more space in an undo segment, there is a fixed algorithm the determines when extents are reused.. The transaction will first attempt to reclaim expired extents from the current segment, then expired extents from another segment. The third method will be to autoextend the datafile(s), if this is set. Next, the unexpired extents from the current segment and other segments will be allocated, as long as the extents do not contain uncommitted transactions. Finally, an error will be raised if none of the methods are successful. As this algorithm indicates, unexpired extents can be reused. This could cause ORA-01555 errors and failures of flashback queries. While much has been made of AUM resolving the Snapshot Too Old issue, the error will continue to haunt DBAs and developers, though the incidence may be reduced. I have seen flashback queries promoted as a database recovery method, it is not guaranteed to work and should not be depended upon.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/19602/viewspace-1020829/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/19602/viewspace-1020829/