 |
|
Data Guard Physical Standby Time Lag
Oracle Tips by Burleson Consulting
December 9, 2011
|
Oracle Data Guard: Physical Standby Databases with
Time Lag
Oracle Data Guard provides functionality to manage the time
lag between delivery of the archived log file on the standby site
and the application of these archived logs. In essence, it builds a
delay between the log transfer and the log apply service on the
physical standby database.
To configure a physical Oracle instance
with
time lag, nothing has to be changed on the physical standby
database; instead, the initialization parameter of the primary
database will have to be altered. On the primary site, change the
log_archive_dest_n parameter to include the DELAY attribute.
The following example will put a delay of 60
minutes between the log transfer and the log apply services on the
physical Oracle instance
identified as appsdbstdby:
ALTER SYSTEM SET
LOG_ARCHIVE_DEST_3=’SERVICE=appsdbstdby DELAY=60’;
The timer starts on the Oracle instance
after
the archived log is received by the standby site.
|
