Question: I am using data guard with
asynchronous log transport mode ( ), and I am getting
LNS
wait on SENDREQ issues. What is the difference between
synchronous (SYNC) mode and asynchronous (ASYNC) log transport
modes? I have a very slow network with 25 milliseconds average
packet shipment time. Which archive redo log transport mode is
best, and why?
Answer: Oracle Data
Guard redo log transport offers synchronous log transport mode (LogXptMode
= 'SYNC') or asynchronous log transport mode (LogXptMode =
'ASYNC'). Systems with a network bottleneck would get
better overall response time with the ASYNC mode, while shops that
cannot tolerate a stale standby server (i.e. maximum availability or
maximum protection are best with the SYNC mode.
The
difference is all about when the COMMIT happens.
- LogXptMode = ('SYNC'): As the name
implies, SYNC mode synchronizes the primary with the standby
database and all DML on the primary server will NOT be committed
until the logs have been successfully transported to the standby
servers. The synchronous log transport mode is required
for the Maximum Protection and Maximum Availability data
protection modes.
- LogXptMode = ('ASYNC'): Conversely,
asynchronous mode (ASYNC) allows updates (DML) to be committed
on the primary server before the log file arrives on the standby
servers. The asynchronous log transport mode is required
for the Maximum Performance data protection mode.
Also see these important notes on
LNS wait on SENDREQ.
|
|
Get the Complete
Oracle SQL Tuning Information
The landmark book
"Advanced Oracle
SQL Tuning The Definitive Reference" is
filled with valuable information on Oracle SQL Tuning.
This book includes scripts and tools to hypercharge Oracle 11g
performance and you can
buy it
for 30% off directly from the publisher.
|