redo buffer

~~~~~~~~~~~~~~~~~~~~~~~~
发生写日志文件的条件
~~~~~~~~~~~~~~~~~~~~~~~~
1.Commit
2.log Buffer is 1/3 full
3.Checkpoint
4.1 Meg of data in log buffer
5.DBWR writes
6.3秒钟[@more@]

~~~~~~~~~~~~~~~~~~~~~~~~
发生写日志文件的条件
~~~~~~~~~~~~~~~~~~~~~~~~
1.Commit
2.log Buffer is 1/3 full
3.Checkpoint
4.1 Meg of data in log buffer
5.DBWR writes
6.3秒钟

跟你redo生成的频率，和redo相关的latch相关
可以查看latch命中率看是不是分配latch有瓶径

redo entries --在log buffer中总的请求次数
redo log space requests --在log buffer中的所有请求次数中等待的次数

select (req.value*5000)/entries.value "Ratio"
from v$sysstat req, v$sysstat entries
where req.name = 'redo log space requests'
and entries.name = 'redo entries';


Ratio
----------
.400664651

应该是没有log buffer space事件最好
redo buffer allocation retries事件也是越少越好，他和redo
entries的比值应该接近0或少于1%，否则要增加redo buffer

监控 SGA 中重做日志缓存区的命中率，应该小于1%

SELECT name, gets, misses, immediate_gets, immediate_misses,
Decode(gets,0,0,misses/gets*100) ratio1,
Decode(immediate_gets+immediate_misses,0,0,
immediate_misses/(immediate_gets+immediate_misses)*100) ratio2
FROM v$latch WHERE name IN ('redo allocation', 'redo copy');

redo allocation,redo copy这个应该是指在redo buffer中分配空间，将redo从server process进程copy到redo buffer中，那这个所谓的命中率应该是指在redo buffer中分配空间的失败率吧

如果redo allocation失败率较高，说明可能redo buffer空间太小，或者lgwr写出redo的速度太慢

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

转载于:http://blog.itpub.net/34329/viewspace-919220/