> The database can contain ASM and NON-ASM files. > ASM files cannot be accessed from OS, more secure and less human errors. > ASM can automatically handle persistent naming for partitions. > ASM can work with any storage (SAN, NAS, SSD, Direct Attached Storage). > ASM can coexist with other storage types.

> Mirroring / Triple mirroring equivalence & Stripping across different storage vendors. > Ability to Dynamically Add and Remove Disk/Space while the database is running. > Raw device performance can improve I/O performance. > When you add/remove disks from a disk group, ASM will automatically redistribute the file contents and eliminates the need for downtime. I/O is spread evenly across all available disk to maximize performance. > Striping level is into Allocation Unit size (AU is the smallest unit in ASM) (1MB by default), opposed to other vendors that do it at the disk level, the thing provides better performance and I/O latency, for ASM. > Mirroring level is into Allocation Unit size (AU is the smallest unit in ASM) (1MB by default), opposed to other vendors that do it at the disk level. > Unlike other vendors, hot spare disks are not required for mirroring, the thing provides more efficient use of the storage capacity. > Adding a new disk to the diskgroup will not only increase the space but will improve the throughput of that diskgroup. > Provides MIRRORING & STRIPPING in the same time for all data across all disks, without any additional work by the DBA. I'll illustrate 'Why ASM?' through Pro's & Con's approach to show you the full image and let you easily judge ASM. In this post I'll try to provide a brief summary for a huge topic like Automatic Storage Management (ASM), hopefully the reader find it useful in understanding ASM.Īutomatic Storage Management ( ASM) is a new feature in Oracle 10g onward provides a state of the art storage for Oracle database files.

Oracleasm renamedisk