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
IBM Bluemix in Germany, includes dashDB and Cloudant
Read the complete post at blog.4loeser.net/…/ibm-bluemix-in-germany-includes-dashdb.html...
How to UPDATE Nested Object and Table Columns, Part 2
The first part of this series showed how you can leverage Oracle’s SQL syntax with UDT columns and collection columns. It would be nice if Oracle gave you some SQL to work with the elements of ADT col...
Using Toad Edge Preview 2.0.0 with PostgreSQL 10 on Amazon ECS Fargate...
Docker has revolutionized software packaging and running. With Docker, software is packaged as Docker images. Applications are run in lightweight Docker containers. Multiple containers run in isolatio...