AMM removing archive logs that haven't been sent to all standby servers

[Mark Weeden]

We have 3 standby servers and have found (rare cases dealing with disk space free threshold) that the one env file designated to perform AMM on the primary server can delete log files that haven't yet been sent to all three standby servers.

I know it does a check to make sure that an archive log have been sent to the server running the AMM but it would be nice to add an additional check to make sure the log has been sent to all standby servers before removing them. The information is all in the current dbvisit tables.

[Arjen Visser]

Hi Mark,
Thank you for suggesting this feature. It is a great feature.

The hard part is to figure out if all of the standby servers are still active because each Dbvisit Standby process to each standby server is an individual process.

So if one Dbvisit Standby process to transfer to a standby server is no longer active because you no longer need it to, and has not transferred a specific log, you still want the other AMM process to remove the log because it is no longer relevant to the inactive standby server.
So there are some exceptions to when you do not want the additional checking.

Any idea of how you could see this working in this exception?

We definitely add this to our feature list. Thanks again.