Log_archive_min_succeed_dest Parameter Is Not Making The Database To Work With One Archivelog Destinations
Last updated on DECEMBER 06, 2016
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
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?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms