Pros/Cons for a Seperate ASM Archivelog Disk Group
607405Mar 21 2008 — edited Oct 7 2008We have a non-ASM best practice of having our archivelogs on their own filesystem. When there is a major problem that fills up this space the datafiles (separate filesystem) themselves are not affected and the backup area used by RMAN (separate filesystem) is fully functional to perform archivelog sweeps.
My DBA team and I have the same concern about having the archivelogs in the FRA along with backups, etc., in the ASM. We are proposing a third disk group just for archivelogs. Also a best practice of always having at least 1 spare disk available that can be added to a disk group in an emergency.
Is there a reason why this is not a good idea or unnecessary? My team is new to ASM and I don't pretend to understand all the real world intracies of Oracle managing the FRA space/archivelogs/rman backups/etc.Thanks for any insight you can offer.