2012-10-15 11gR2 concepts page 216 - 244

In-Doubt Transactions
The recoverer (RECO) background process automatically resolves the outcome of
in-doubt distributed transactions. After the failure is repaired and communication is
reestablished, the RECO process of each local Oracle database automatically commits
or rolls back any in-doubt distributed transactions consistently on all involved nodes.

以前经常看到11G的后台有个RECO进程，原来是这个作用。恢复一些失败的事务。

 

Use of Control Files -- 控制文件的作用
A control file contains information such as -- 它记录了以下的内容
the following:
 -- The database name and database unique identifier (DBID)
 -- The time stamp of database creation
 -- Information about data files, online redo log files, and archived redo log files
 -- Tablespace information
 -- RMAN backups

Structure of the Online Redo Log -- 日志文件的结构
The redo records have all relevant metadata for the change, including the following:
 -- SCN and time stamp of the change
 -- Transaction ID of the transaction that generated the change
 -- SCN and time stamp when the transaction committed (if it committed)
 -- Type of operation that made the change
 -- Name and type of the modified data segment

 

Overview of Data Blocks -- 数据块
Oracle Database manages the logical storage space in the data files of a database in
units called data blocks, also called Oracle blocks or pages. A data block is the
minimum unit of database I/O.

把这段摘下来，源于PAGES，我好像在哪看过， BLOCKS = PAGES。

 

Data Block Format

 

Data Block Overhead
Oracle Database uses the block overhead to manage the block itself. The block
overhead is not available to store user data. As shown in Figure 12–6, the block
overhead includes the following parts:
 -- Block header 块头
This part contains general information about the block, including disk address and
segment type. For blocks that are transaction-managed, the block header contains
active and historical transaction information.
A transaction entry is required for every transaction that updates the block. Oracle
Database initially reserves space in the block header for transaction entries. In data
blocks allocated to segments that support transactional changes, free space can
also hold transaction entries when the header space is depleted. The space
required for transaction entries is operating system dependent. However,
transaction entries in most operating systems require approximately 23 bytes.
 -- Table directory 表目录
For a heap-organized table, this directory contains metadata about tables whose
rows are stored in this block. Multiple tables can store rows in the same block.
 -- Row directory  行目录
For a heap-organized table, this directory describes the location of rows in the data
portion of the block.
After space has been allocated in the row directory, the database does not reclaim
this space after row deletion. Thus, a block that is currently empty but formerly
had up to 50 rows continues to have 100 bytes allocated for the row directory. The
database reuses this space only when new rows are inserted in the block.
Some parts of the block overhead are fixed in size, but the total size is variable. On
average, the block overhead totals 84 to 107 bytes.