Oracle RBA(Redo Byte Address) 说明

2024-04-04 02:38
文章标签 oracle 说明 address byte redo rba

本文主要是介绍Oracle RBA(Redo Byte Address) 说明,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

 

一. RBA 说明

之前整理了一个rdba和dba 的说明文档,参考:

       Oracle rdba和 dba 说明

       http://blog.csdn.net/tianlesoftware/article/details/6529346

 

       在MOS的文档:Question About RBA (Redo Block Address) [ID 759966.1] 有对RBA的说明。

 

       A"Redo Block Address" (RBA) describes a physical location within aredo log file.

 

RBA 由以下三部分组成:

       (1)the log file sequence number (4 bytes)

       (2)the log file block number (4 bytes)

       (3)the byte offset into the block at which the redo record starts (2bytes)

 

如:RBA[0x19.2.10] 代表 Log squence25, Block number 2 with byte offset 16.

注意这里的格式:都是16进行。

 

Redo 与checkpoint 关系很大,当设置log_checkpoints_to_alert 参数为true后,checkpoint 发生时会写入alert log里。

 

如:

SYS@dave2(db2)>alter system set log_checkpoints_to_alert=true scope=both;

System altered.

SYS@dave2(db2)> alter system switchlogfile;

System altered.

 

log里的信息如下:

Thu Aug 18 18:46:18 2011

ALTER SYSTEM SETlog_checkpoints_to_alert=TRUE SCOPE=BOTH;

Thu Aug 18 18:48:07 2011

Beginning log switch checkpoint up to RBA[0xa.2.10], SCN: 2148380730

Thread 1 advanced to log sequence 10

 Current log# 3 seq# 10 mem# 0: /u01/app/oracle/oradata/dave2/redo03.log

Thu Aug 18 18:52:54 2011

Completed checkpoint up to RBA [0xa.2.10],SCN: 2148380730

Thu Aug 18 19:08:59 2011

Incremental checkpoint up to RBA[0xa.736.0], current log tail at RBA [0xa.80a.0]

Thu Aug 18 19:39:01 2011

Incremental checkpoint up to RBA[0xa.c96.0], current log tail at RBA [0xa.d7c.0]

....

Fri Aug 19 07:10:00 2011

Incremental checkpoint up to RBA[0xa.1688a.0], current log tail at RBA [0xb.8328.0]

Fri Aug 19 07:11:04 2011

Completed checkpoint up to RBA [0xb.2.10],SCN: 2148412930

Fri Aug 19 07:40:02 2011

Incremental checkpoint up to RBA[0xb.896c.0], current log tail at RBA [0xb.89c1.0]

  

 

       根据我们前面的说明,RBA 由三部分组成,第一部分是sequence number,即序列号。

 

在我们贴出来的log里有2个日志序列:RBA [0xa.1688a.0] 和 RBA [0xb.896c.0]。

SYS@dave2(db2)> select to_number('a','xx')from dual;

 

TO_NUMBER('A','XX')

-------------------

                 10

 

SYS@dave2(db2)> selectto_number('b','xxx') from dual;

 

TO_NUMBER('B','XXX')

--------------------

                  11

 

a 对应的是日志序列10,b 对应的是日志序列11.

 

SYS@dave2(db2)> select sequence# fromv$archived_log;

 

 SEQUENCE#

----------

        1

        2

        3

        4

        5

        6

        7

        8

        9

       10

 

SYS@dave2(db2)> select sequence#,group#,status from v$log;

 

 SEQUENCE#    GROUP# STATUS

---------- ---------- ----------------

       11          1 CURRENT

        9          2 INACTIVE

       10          3 INACTIVE

 

根据这个查询结果判断10是已经归档的,11是正在使用的current redo log file。

 

第二部分就是我们对应的block:

SYS@dave2(db2)> selectto_number('1688a','xxxxxxxxx') from dual;

 

TO_NUMBER('1688A','XXXXXXXXX')

------------------------------

                         92298

 

在之前的blog:

       Oracle Dump Redo Log File 说明

       http://blog.csdn.net/tianlesoftware/article/details/6670962

 

里提到,可以根据RBA 来dump redo block:

 

格式如下:

ALTER SYSTEM DUMP LOGFILE 'filename' RBAMIN seqno .blockno RBA MAX seqno . blockno;

 

 示例:

SYS@anqing1(rac1)> alter system dumplogfile'+data/anqing/onlinelog/redo02.log'  rbamin 121 10458  rba max125 10472;

System altered.

 

这里的参数:seqno .blockno; 就是我们RBA中的前2部分。

 

二. RBA 使用

       RBAs are not necessarily unique within their thread, because the log file sequencenumber may be reset to 1 in all threads if a database is opened with theRESETLOGS option.

 

RBAs are used in the following important ways.

       With respect to a dirty block in thebuffer cache, the low RBA is theaddress of the redo for the first change that was applied to the block since itwas last clean, and the high RBA is the address of the redo for the most recent change to have been applied to theblock.

      

       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 thecheckpoint queues if incremental checkpointing is enabled -- otherwise it isthe 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. In stance recovery, when needed, begins from the checkpoint RBA recorded in thecontrolfile. 

 

       The target RBA is the point up to which DBWnshould 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 ablock for which the high RBA is beyond the on-disk RBA. Otherwise transactionrecovery (rollback) would not be possible, because the redo needed to undo achange is always in the same redo record as the redo for the change itself.

 

       The term sync RBA is sometimes used to referto the point up to which LGWR is required to sync the thread. However, this isnot a full RBA -- only a redo block number is used at this point.

 

在上面提到的几种RBA 值可以通过X$BH,和 X$KCCRT 视图进行查看:

       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 ofpartial block recovery by PMON.)

       The incremental checkpoint RBA, the target RBA and theon-disk RBA can all be seen in X$TARGETRBA. The incremental checkpointRBA and the on-disk RBA can also be seen in X$KCCCP.

       The full thread checkpoint RBA can be seen in X$KCCRT.

 

 

 

 

 

-------------------------------------------------------------------------------------------------------

QQ:492913789

Email:ahdba@qq.com

Blog:  http://www.cndba.cn/dave

Weibo:   http://weibo.com/tianlesoftware

Twitter:  http://twitter.com/tianlesoftware

Facebook: http://www.facebook.com/tianlesoftware

Linkedin: http://cn.linkedin.com/in/tianlesoftware

DBA1 群:62697716(满);   DBA2 群:62697977(满)  DBA3 群:62697850(满)  

DBA 超级群:63306533(满);  DBA4 群: 83829929(满) DBA5群: 142216823(满) 

DBA6 群:158654907(满)  聊天 群:40132017(满)   聊天2群:69087192(满)

--加群需要在备注说明Oracle表空间和数据文件的关系,否则拒绝申请

这篇关于Oracle RBA(Redo Byte Address) 说明的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/874608

相关文章

Tomcat版本与Java版本的关系及说明

《Tomcat版本与Java版本的关系及说明》:本文主要介绍Tomcat版本与Java版本的关系及说明,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录Tomcat版本与Java版本的关系Tomcat历史版本对应的Java版本Tomcat支持哪些版本的pythonJ

Nginx指令add_header和proxy_set_header的区别及说明

《Nginx指令add_header和proxy_set_header的区别及说明》:本文主要介绍Nginx指令add_header和proxy_set_header的区别及说明,具有很好的参考价... 目录Nginx指令add_header和proxy_set_header区别如何理解反向代理?proxy

Oracle存储过程里操作BLOB的字节数据的办法

《Oracle存储过程里操作BLOB的字节数据的办法》该篇文章介绍了如何在Oracle存储过程中操作BLOB的字节数据,作者研究了如何获取BLOB的字节长度、如何使用DBMS_LOB包进行BLOB操作... 目录一、缘由二、办法2.1 基本操作2.2 DBMS_LOB包2.3 字节级操作与RAW数据类型2.

查看Oracle数据库中UNDO表空间的使用情况(最新推荐)

《查看Oracle数据库中UNDO表空间的使用情况(最新推荐)》Oracle数据库中查看UNDO表空间使用情况的4种方法:DBA_TABLESPACES和DBA_DATA_FILES提供基本信息,V$... 目录1. 通过 DBjavascriptA_TABLESPACES 和 DBA_DATA_FILES

Java实现将byte[]转换为File对象

《Java实现将byte[]转换为File对象》这篇文章将通过一个简单的例子为大家演示Java如何实现byte[]转换为File对象,并将其上传到外部服务器,感兴趣的小伙伴可以跟随小编一起学习一下... 目录前言1. 问题背景2. 环境准备3. 实现步骤3.1 从 URL 获取图片字节数据3.2 将字节数组

JAVA SE包装类和泛型详细介绍及说明方法

《JAVASE包装类和泛型详细介绍及说明方法》:本文主要介绍JAVASE包装类和泛型的相关资料,包括基本数据类型与包装类的对应关系,以及装箱和拆箱的概念,并重点讲解了自动装箱和自动拆箱的机制,文... 目录1. 包装类1.1 基本数据类型和对应的包装类1.2 装箱和拆箱1.3 自动装箱和自动拆箱2. 泛型2

MySQL常见的存储引擎和区别说明

《MySQL常见的存储引擎和区别说明》MySQL支持多种存储引擎,如InnoDB、MyISAM、MEMORY、Archive、CSV和Blackhole,每种引擎有其特点和适用场景,选择存储引擎时需根... 目录mysql常见的存储引擎和区别说明1. InnoDB2. MyISAM3. MEMORY4. A

MyBatis的配置对象Configuration作用及说明

《MyBatis的配置对象Configuration作用及说明》MyBatis的Configuration对象是MyBatis的核心配置对象,它包含了MyBatis运行时所需的几乎所有配置信息,这个对... 目录MyBATis配置对象Configuration作用Configuration 对象的主要作用C

Oracle登录时忘记用户名或密码该如何解决

《Oracle登录时忘记用户名或密码该如何解决》:本文主要介绍如何在Oracle12c中忘记用户名和密码时找回或重置用户账户信息,文中通过代码介绍的非常详细,对同样遇到这个问题的同学具有一定的参... 目录一、忘记账户:二、忘记密码:三、详细情况情况 1:1.1. 登录到数据库1.2. 查看当前用户信息1.

在Dockerfile中copy和add的区别及说明

《在Dockerfile中copy和add的区别及说明》COPY和ADD都是Dockerfile中用于文件复制的命令,但COPY仅用于本地文件或目录的复制,不支持自动解压缩;而ADD除了复制本地文件或... 目录在dockerfile中,copy 和 add有什么区别?COPY 命令ADD 命令总结在Doc