Tune your Oracle Automatic Storage Management（优化您的Oracle自动存储管理）.pdfVIP

Tune your Oracle Automatic Storage Management Tips Techniques at implementing and optimizing your database storage using Oracle ASM in a SAN environment by Thiru Vadivelu Implementing Oracle’s Automatic Storage Management in a Storage Area Network environment can be an interesting and involved task. The purpose of this document is to provide some generic guidelines and things to consider/configure when setting up/migrating to Oracle Automatic Storage Management (ASM), in a SAN environment, based on our past experiences. This article is primarily intended for DBAs, Database Managers, System administrators and Storage administrators. Why ASM? • ASM is an Oracle provided Database/Cluster filesystem and Storage Volume manager, optimized for Oracle for any kind of workload (be it OLTP or DSS or Batch, sequential or random access), built-in with the database, with no additional cost. • It follows SAME (Stripe and Mirror Everything) strategy, eliminating any database level IO hotspots, as the database files are striped equally across all the available disks in the allocated disk groups and are dynamically rebalanced with the addition and removal of disks online. • ASM provides for better storage utilization and storage consolidation (ie allows multiple databases on the same Server or across multiple Servers to share storage through Oracle clusterware). • It allows leveraging existing storage RAID technologies (Mirroring, RAID 5 etc) to provide for additional striping and redundancy. • It can leverage IO multipathing technologies (like EMC Powerpath, Hitachi HDLM etc) to provide for better IO balancing and fault-tolerance. • Makes use of Oracle ‘Kernel Service Direct File (ksfd)’ interface to perform KAIO (kernel asynchronous IO) against raw devices by-passing OS page cache, providing the best IO performance with no overhead from Operating sys