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
Now NOT to Handle Exceptions
Oracle Database raises an exception when something goes wrong (examples: divide by zero, duplicate value on unique index, value too large to fit in variable, etc.). You can also raise exceptions when ...
Rising Above Without Sinking Below
Rising Above The data professionals I've had the honor of working with are some of the most dedicated people I know. There have been several occasions in my life when a hard deadline has been mandate...
Why do members of a redo log show up red in the redo log manager? I...
If the entry is red, then either the redo log size does not match the size of the other redo logs or there is a missing file. The count of the members should be the same across all the groups....
