High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

ARCHIVE_LAG_TARGET setting and data guard real time apply

Hello,

We have been using this archive_lag_target parameter to guarantee log switch happens every 15 minutes or so and guaranteeing the standby will not fall behind more than 15 minutes.

Now we have set up Active data guard with real time apply using standby redo logs and the changes are propagated immediately. In this situation do we really need archive_lag_target settings in the primary database?

In my opinion that is not needed, any issues anybody sees?

Thanks

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center