log file parallel write

以下是metalink中关于log file parallel write的一段说明：

 

This wait event is used when waiting for the writes of redo records to the redo log files
to complete. The waits occur in log writer (LGWR) as part of normal activity of copying
records from the redo log buffer to the current online log

 

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.

 

如果STATUS是ACTIVE模式，说明该表空间正在备份。
由于表空间的热备会产生大量的redo，所以尽量在业务不繁忙的时候进行备份。

SQL> SELECT D.TABLESPACE_NAME, V.STATUS
  2    FROM V$BACKUP V, DBA_DATA_FILES D
  3   WHERE D.FILE_ID = V.FILE#;

TABLESPACE_NAME    STATUS
--------------------------  ----------------
LIANG                          NOT ACTIVE
USERS                         ACTIVE

 

 

--停止表空间的热备份：
SQL>alter tablespace USERS begin backup;
表空间已更改。

 

 

--停止users表空间的热备份后，status由ACTIVE变为NOT ACTIVE

SQL> SELECT D.TABLESPACE_NAME, V.STATUS
  2    FROM V$BACKUP V, DBA_DATA_FILES D
  3   WHERE D.FILE_ID = V.FILE#;

TABLESPACE_NAME    STATUS
-----------------------     ----------------
LIANG                        NOT ACTIVE
USERS                      NOT ACTIVE

 

2.Redo log members should ideally be on high speed disks
eg: RAID5 is not a good candidate for redo log members.
用RAID0 或RAID 0+1或许会更好。

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)
NOLOGGING / UNRECOVERABLE operations may be possible for certain operations to
reduce the overall rate of redo generation
(NOLOGGING可能会降低redo，但恢复起来比较麻烦)