The log_archive_duplex_dest parameter allows you to define not one but two archived redo log storage locations. You can define it as a can or must succeed operation by setting the log_archive_min_succeed_dest parameter. This second parameter, if set to 1, does not require that the archived redo log copy to the duplex destination be complete; otherwise, if the parameter is set to a 2, both copies must be successful. If the parameter is set to 2, the database halts until the reason that the archive log cannot be copied is corrected.
Related Articles
PostgreSQL for Enterprises – Part V
In this article series, we are exploring why and how enterprises are starting to use PostgreSQL. The open-source PostgreSQL is a database more than 20 years old and owned by the Postgres foundation. I...
SYSBACKUP and SYSDG permissions in Oracle 12c
Introduction In many companies there is a clear separation of duties for various Oracle Database related tasks such as administering ASM and backing up/restoring Oracle databases. In the past, DBAs us...
Overview of developer features in Toad for DB2 – Part III
This video on database map drag and drop is part three of an overview of developer features in Toad for DB2....
