Forced Log Switching and delayed physical standby
edited Apr 8, 2013 9:17AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 7 commentsAnswered
We are using a physical standby database on a 48 hour lag using the log_archive_dest_1 with the DELAY=2880 which is working fine .. however based on our traffic our logs switch every 30-60 minutes during normal business hours, but through out the evening and over the weekends we don't have the traffic to even switch once. In our development area we looked at using the lag_archive_target and set it to 30 minutes hoping this would force the logs to switch to minimize potential data loss down to 30 minutes or so but still enable us to keep the lag as desired.
0