Oracle Log Block Size

Although the size of redo entries is measured in bytes, LGWR writes the redo to the log files on disk in blocks. The size of redo log blocks is fixed in the Oracle source code and is operating system specific. Oracle‘s documentation uses the term "operating system block size" to refer to the log block size. Normally it is the smallest unit of I/O supported by the operating system for raw I/O, but on some operating systems it is the smallest possible unit of file system based I/O. The following table shows the most common log block sizes and some of the operating systems that use them.

  Log Block Size   Operating Systems
512 bytes   Solaris, AIX, Windows NT/2000, Linux, Irix, DG/UX, OpenVMS, NetWare, UnixWare, DYNIX/ptx  
1024 bytes   HP-UX, Tru64 Unix
2048 bytes   SCO Unix, Reliant Unix
4096 bytes   MVS, MPE/ix

The log block size is the unit for the setting of the log_checkpoint_interval_log_io_size and max_dump_file_size parameters. Therefore, it is an important constant to know. If your operating system is not listed in the table above, then you can find your log block size using the following query.

select max(lebsz) from sys.x$kccle;

This query is available as the APT script log_block_size.sql. If your operating system is not listed in the table above, please click on the feedback icon below and send us an email so that we can add it to the list.

The log block size can also be inferred from the system statistics in StatsPack reports. There is a 16 byte header for each log block, and the size of the data area is approximately the number of bytes of redo generated (redo size) plus the number of bytes of redo space left unused (redo wastage) divided by the number of log blocks written (redo blocks written). Thus the approximate formula is

16 + (redo size + redo wastage) / redo blocks written

This formula will commonly understate the log block size by a few bytes, because it does not allow for redo that has been generated but not yet written, and the redo size statistic is commonly a little inaccurate.

原文地址:https://www.cnblogs.com/lhdz_bj/p/9708716.html

时间: 2024-10-30 20:21:36

Oracle Log Block Size的相关文章

Oracle corrupt block(坏块) 详解

转自:http://blog.csdn.net/tianlesoftware/article/details/5024966 一. 坏块说明 1.1 相关链接 在看坏块之前,先看几个相关的链接,在后面的说明中,会用到链接中的一些内容. ORA-600 各个参数含义说明 http://blog.csdn.net/tianlesoftware/article/details/6645809 Oracle 不同故障的恢复方案 http://blog.csdn.net/tianlesoftware/ar

一旦rhel5.8造成只读文件系统ORA-00354: corrupt redo log block header

Wed Jun 03 03:31:24 CST 2015 Thread 1 advanced to log sequence 396 (LGWR switch) Current log# 3 seq# 396 mem# 0: /u01/app/oracle/oradata/orcl/redo03.log Wed Jun 03 19:05:48 CST 2015 Thread 1 advanced to log sequence 397 (LGWR switch) ----------------

ORA-00349: failure obtaining block size for '+fra_grp01_d

有一次恢复库以后,open时报错ORA-00349,例如以下.最后通过删除这个log group解决. SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-00349: failure obtaining block size for '+fra_grp01_d select group#,name,bytes,status from v$logfile; SQL> /

uwsgi部署到nginx出现invalid request block size: 4161 (max 4096)...skip问题

使用Flask制作一个网页平台之后,登陆使用openid登陆,然后使用uwsgi服务部署到nginx上,运行起来没有什么问题,但是偶尔在登陆的时候出现502的错误,一般登陆成功之后后面的任何操作都不会出错. 查看uwsgi的log之后,发现出现这样的一个错误: invalid request block size: 4161 (max 4096)...skip 之前一个没有去详细搜索过,也没有具体去看错误产生的原因,因为只是偶尔出现,并且有时候重试的时候是可以登陆的,所以没有太多的去关注,今天因

ORA-00349: failure obtaining block size for '+fra_grp01_d

有一次恢复库以后,open时报错ORA-00349,如下.最后通过删除这个log group解决. SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-00349: failure obtaining block size for '+fra_grp01_d select group#,name,bytes,status from v$logfile; SQL> / 1

解决Virtual Box 下安装Mac OS X时出现的“hfs: summary table not allowed on FS with block size of 2048”问题

安装的时候首先出现 hfs: summary table not allowed on FS withblock size of 2048 错误,然后就是 hfs: could not initializc summary table forOSX Base System 错误. 一开始也不知道是怎么回事,后来在yandex上搜索中找到一篇帖子,它说这是CPU的问题.Mac OS X 10.9不能识别特有的CPU格式,只能识别一部分.于是呢,按照帖子中的做法,首先找到Virtual Box的位置

4K Block Size的Device和 Aligned IO

http://www.cnblogs.com/cenalulu/p/3587006.html 背景:最近采购了一批新的服务器,底层的存储设备的默认physical sector size从原有的 512B 改为了 4K. 装完系统以后,在做数据库物理备份恢复时xtrabackup报了这么一个错.但是同样的备份在512B sector size的老系统上却可以恢复. 报错如下: InnoDB: Error: tried to read 2048 bytes at offset 0 0.InnoDB

kdbchk: the amount of space used is not equal to block size

一.对数据文件检查 注意:应该在关闭数据库模式下进行bbed的操作 [[email protected] controlfile]$ dbv file=/u01/app/oracle/oradata/ORCL/datafile/test_01.dbf blocksize=8192 DBVERIFY: Release 10.2.0.1.0 - Production on Fri Jan 16 23:05:01 2015 Copyright (c) 1982, 2005, Oracle. All r

Oracle log files Troubleshooting Oracle

Oracle log files The following Oracle log files are helpful for resolving issues with Oracle components: Table: Log files for Oracle RAC 10g Release 2 Table: Log files for Oracle RAC 11g Release 2 and later versions Table: Log files for Oracle databa