undo segment的创建、online以及extent的分配原则

When the undo tablespace is created, a number of undo segments are created. These are named using the _SYSSMU$ algorithm. Because of the new name, some commands (alter system dump undo header) require that the undo segment name be enclosed in double quotes.

The number of undo segments created and brought online is a function of the SESSIONS parameter. The algorithm is roughly 1 undo segment for each 5 sessions. All undo segments are placed online when the sessions parameter is set to 46 or greater. The lower limit was not tested, as the minimum value for the sessions parameter in the test database was 16, which was derived from the minimum number of processes (10) for the database. These are sized according to the autoallocate algorithm for locally managed tablespaces. The basic algorithm is that the first 16 extents are 64k in size. The subsequent allocation method is the next 63 extents of 1m, the next 120 extents of 8m and all additional extents at 64m.

The first block of the first undo extent is reserved as the header and not indicated in the data dictionary views. As with Oracle 8, the second block of the undo segment is not used initially and may or may not be allocated at a later time. This is one of those anomalies that has no consistent pattern and is therefore hard to explain.

 

当undo表空间被创建时，很多的undo segments被创建，这些segments以_SYSSMU$
规则来命名。 因为新的名称，一些命令比如alert system dump undo header 需要在
undo segment的名称上加注双引号。

Undo segment创建和在线数量是由参数SESSIONS决定的，粗略算法为每5个session对应
一个undo segment, 当sessions参数设置为46或更大时所有的undo segments都处于
online状态。 下限没有被测试过，因为在测试数据库中sessions参数最小值是16，
这个值来自于数据库中参数processes的最小值10，这些大小是参考本地管理表空间
(LMT)自动分配算法而来。 基本算法是： 前16个extents大小为64K, 随后63个extents
是每个1M, 然后120个extents是每个8M, 再后面的extents大小都是64M不变。

第一个undo extent的第一个block保留作为头部，没有在数据字典中标示出来，与Oracle
8 一样，undo segment的第二个block最初没有被使用，后面一段时间也许被分配，也许
不会，这是异常现象之一，没有统一的模式，因此很难解释。 

 

查询undo segment ：  

select segment_name,segment_id,status from dba_rollback_segs order by status

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

转载于:http://blog.itpub.net/35489/viewspace-676240/