Question about log file sync in DataGuard

From: Michael Schmitt <mschmitt_at_uchicago.edu>
Date: Fri, 12 Oct 2012 18:33:45 +0000
Message-ID: <1184E7EFAB1D1C47A5038D06F64BE92602054304_at_XM-MBX-02-PROD.ad.uchicago.edu>



Hello,

I am hoping the list can help me better understand the waits I am seeing for log file sync in a Data Guard environment.

This is for an 11.1.0.7 database running on Linux and running in max availability mode (LGWR SYNC)

We consistently see "log file sync" as the top wait event in AWR reports taking 30-40% of the DB time.

A two hour report today showed 1,938 seconds for log file sync.

The report also indicates the following background wait events.

LGWR-LNS wait on channel:	707(s)
LNS wait on SENDREQ:		680(s)
log file parallel write:	667(s)

I am trying to get a better understanding of the break down on the "log file sync". My understanding is that 667(s) of the "log file sync" time is spent on "log file parallel write" waiting for the LGWR on the primary database to write to the redo logfile on the primary server. That would leave ~ 1271(s) time of the reported "log file sync" left. Are the "LGWR-LNS wait on channel" and "LNS want on SENDREQ" basically reporting on the same thing (sending data to standby and waiting for confirmation) or are those two distinct functions? I was thinking that they might be the same function and that approximately 564(s) of the "log file sync" time was just multiple sessions reporting the "log file sync" wait.

Any advice on better understanding this would be appreciated

Mike       

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Oct 12 2012 - 20:33:45 CEST

Original text of this message