等待事件：log file parallel write

等待事件log file parallel write是等待redo records写入redo log file完成，是数据库正常活动的一部分，将redo buffer中的redo records拷贝到当前的redo log file中。

log file parallel write的参数：

P1 = files（Number of files written to.）

如果每个联机日志组有一个或多个日志成员，那么这些日志成员（log member）是被并行写入redo records的。该参数显示的就是每组写日志成员的数目。

（If you have more than one log member per group then the files are written to in parallel(if possible).This is the number of redo log members(files) that are writes apply to.）

P2 = blocks（Number of blocks to be written.）

写入每个log member中的redo blocks的数目.

（The number of REDO blocks being written to each log member.eg:A value of 10 indicates 10 redo blocks for each log member.）
P3 = requests（Number of I/O requests.）

不同I/O请求的数目。

（The number of distinct IO requests.The number of blocks to be written is divided up into a number of IO requests.）

真正的等待时间是所有未完成的I/O请求完成所花费的事件。尽管写redo log file的操作可能是并行处理的，LGWR需要等待最后的磁盘I/O写操作完成，才认为是完成。因此这个等待事件依赖于OS处理完所有的请求所花费的时间。

以下是Oracle为了减少log file parallel write等待的措施：

You might want to reduce "log file parallel write" wait times in order to reduce user waits which depend on LGWR.

1、Ensure tablespaces are NOT left in HOT BACKUP mode longer than needed.
Tablespaces in HOT BACKUP mode cause more redo to be generated for each change which can vastly increase the rate of redo generarion.

2、Redo log members should ideally be on high speed disks
eg: RAID5 is not a good candidate for redo log members.

3、Redo log members should be on disks with little/no IO activity from other sources.
(including low activity from other sources against the same disk controller)

4、NOLOGGING / UNRECOVERABLE operations may be possible for certain operations to reduce the overall rate of redo generation

[@more@]

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

转载于:http://blog.itpub.net/25748672/viewspace-1049311/