Redo Byte Address (RBA)(轉)
Redo Byte Address (RBA)
Recent entries in the redo thread of an Oracle instance are addressed using a 3-part redo byte address, or RBA. An RBA is comprised of- the log file sequence number (4 bytes)
- the log file block number (4 bytes)
- the byte offset into the block at which the redo record starts (2 bytes)
RBAs are used in the following important ways.
With respect to a dirty block in the buffer cache, the low RBA is the address of the redo for the first change that was applied to the block since it was last clean, and the high RBA is the address of the redo for the most recent change to have been applied to the block.The low and high RBAs for dirty buffers can be seen in X$BH. (There is also a recovery RBA which is used to record the progress of partial block recovery by PMON.) The incremental checkpoint RBA, the target RBA and the on-disk RBA can all be seen in X$TARGETRBA. The incremental checkpoint RBA and the on-disk RBA can also be seen in X$KCCCP. The full thread checkpoint RBA can be seen in X$KCCRT.Dirty buffers are maintained on the buffer cache checkpoint queues in low RBA order. The checkpoint RBA is the point up to which DBWn has written buffers from the checkpoint queues if incremental checkpointing is enabled -- otherwise it is the RBA of last full thread checkpoint. The checkpoint RBA is copied into the checkpoint progress record of the controlfile by the checkpoint heartbeat once every 3 seconds. Instance recovery, when needed, begins from the checkpoint RBA recorded in the controlfile. The target RBA is the point up to which DBWn should seek to advance the checkpoint RBA to satisfy instance recovery objectives.
The on-disk RBA is the point up to which LGWR has flushed the redo thread to the online log files. DBWn may not write a block for which the high RBA is beyond the on-disk RBA. Otherwise transaction recovery (rollback) would not be possible, because the redo needed to undo a change is always in the same redo record as the redo for the change itself.
The term sync RBA is sometimes used to refer to the point up to which LGWR is required to sync the thread. However, this is not a full RBA -- only a redo block number is used at this point.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/756652/viewspace-242283/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Solidity String轉byte32 byte轉StringSolid
- float與byte[]互相轉換
- Java 中將 Short 轉換為 byte[]Java
- python str與byte轉換 encode decodePython
- C#:檔案、byte[]、Stream相互轉換C#
- 【基礎語法】short、int、long轉為byte
- String和byte互轉,Base64正逆向
- Java中String和byte型別互相轉換Java型別
- golang []byte和string的高效能轉換Golang
- java 基礎型別與byte[]的轉換Java型別
- 【REDO】Oracle redo advice-sqlOracle RedoSQL
- 【REDO】Oracle redo undo 學習Oracle Redo
- 網路基礎知識 Network Address Translations 網路地址轉換
- 【REDO】Oracle redo內部結構Oracle Redo
- GO語言中string和[]byte的區別及轉換Go
- 如何在 Go 中將 []byte 轉換為 io.Reader?Go
- [LeetCode] Validate IP AddressLeetCode
- Golang 陣列和字串之間的相互轉換[]byte/stringGolang陣列字串
- MySQL redoMySql
- C#位元組陣列byte[]和字串string如何互相轉換C#陣列字串
- C/C# float與byte/u8 陣列的轉化C#陣列
- mysql bind_address如何配置多個地址 mysql bind-address選項MySql
- Oracle Redo and UndoOracle Redo
- MySQL:Redo & binlogMySql
- go byte和runeGo
- 《A Byte of Vim》書評
- Invalid byte 3 of 3-byte UTF-8 sequence 解決方案
- cluster-wide IP address managementIDE
- ORA-00130: invalid listener address
- Oracle redo解析之-1、oracle redo log結構計算Oracle Redo
- byte轉16進位制String時為什麼要乘上0xff
- LPDDR4 byte mode
- 關於Byte和bit
- golang 的 rune 和 byteGolang
- 走進 JDK 之 ByteJDK
- mysql之 redo logMySql
- C# convert ImageSource to byte arrayC#
- oracle的redo和undoOracle