Log_archive_min_succeed_dest Parameter Is Not Making The Database To Work With One Archivelog Destinations
(Doc ID 1669589.1)
Last updated on FEBRUARY 20, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Goal
Writing archivelogs on two different locations. One is the FRA, which resides in ASM and the other one is an NFS mount on an external storage. Also setting "log_archive_min_succeed_dest" to 1.
If external storage crashed the database became unavailable.
Why the database was not working anymore, just because one of the archivelog destinations was gone since log_archive_min_succeed_dest parameter should prevent that from happening.
Is this expected behaviour? Is there a way to prevent this from happening again next time the storage might fail?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |