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
How I became an author, how it helped my career–and how you can do it too
Hi, This is the time of year we look back and consider what we’re thankful for. I am thankful for the opportunity to be well-published. I have always enjoyed sharing my knowledge with others and I ha...
Changes to the connection manager in Toad for DB2
This video walks through changes to the connection manager in Toad for DB2....
Oracle 12.2 In-memory New Features
I was able to attend the Oracle Open World 2016 event this past fall. Last April, I posted a nice series on In-memory, material I had gathered from Oracle PM Andy Revenes (heck of a nice guy). Here a...