Oracle Internal & Oracle Academy Use Only Oracle Database 12c: Oracle Automatic Storage Management Administration Activity Guide DGC10 Edition. Automatic Storage Management is a new feature in Oracle ASM was specifically designed to operate with Oracle database files. ASM is http://www tvnovellas.info Oracle Automatic Storage Management (ASM) is a well-known, largely used multi -platform volume manager and file system, designed for.
|Language:||English, Spanish, Hindi|
|ePub File Size:||19.69 MB|
|PDF File Size:||16.33 MB|
|Distribution:||Free* [*Sign up for free]|
Oracle Database 10g - Automatic Storage Management. ASM Addresses these Challenges. DBA Storage Management Challenges. Automatic Storage. Oracle Automatic Storage Management Administrator's Guide, 11g Release 2 ( ) . Oracle Automatic Storage Management 11g Release 2 () New. Performance expert in a box. • Integrate all managers together. • Automatically provides database-wide performance diagnostic, including RAC. • Real-time.
All rights reserved. Manufactured in the United States of America. Except as permitted under the United States Copyright Act of , no part of this publication may be reproduced or distributed in any form or by any means, or stored in a database or retrieval system, without the prior written permission of the publisher. All trademarks are trademarks of their respective owners. Rather than put a trademark symbol after every occurrence of a trademarked name, we use names in an editorial fashion only, and to the benefit of the trademark owner, with no intention of infringement of the trademark.
With ASM, less effort is required for managing your database storage environment. ASM is easier to manage than conventional file systems, it optimizes the performance of your storage hardware, and is tightly integrated with the Oracle Database. Additionally, ASM eliminates the need for 3rd-party volume managers and file systems for managing the Oracle database files.
ASM improves manageability by simplifying storage provisioning, storage array migration, and storage consolidation. In addition to providing ease of management, ASM provides sustained best in class performance because of its innovative rebalancing feature.
ASM distributes data evenly across all storage resources after storage configuration changes, providing an even distribution of IO and optimal performance. ASM scales to very large databases efficiently without compromising functionality or performance.
ASM is built to maximize database availability. ASM provides self-healing automatic mirror reconstruction and resynchronization, rolling upgrades and patching. ASM also supports dynamic and on-line storage reconfigurations in both single instance and Oracle RAC database configurations. ASM customers realize significant cost savings and achieve lower total cost of ownership because of features such as just-in-time provisioning, and clustered pool of storage making it ideal for database consolidation.
ASM provides all of this without additional license or licensing fees. In summation, ASM is a file system and volume manager optimized for Oracle database files providing: Simplified and automated storage management Increased storage utilization, uptime, and agility Delivering predictable performance and availability service levels Total Storage Management for the Oracle Platform With Oracle Database Release ACFS simplifies and automates storage management functions, increases storage utilization, uptime and agility to deliver predictable performance and availability for file data stored outside an Oracle Database.
Automatic Storage Management Cluster File System provides advanced data services and security features for managing general purpose files. Oracle Grid Infrastructure provides an integrated foundation for database and general purpose files as well as an infrastructure for clustered environments. The Oracle Grid Infrastructure streamlines management of volumes, file systems and cluster configurations, therefore eliminating the need for multiple 3rd party software layers that would add complexity and cost.
ASM eliminates hot spots by evenly distributing data providing the optimal bandwidth that an end user or an application needs Arvind Gidwani, Senior Manager IT, Qualcomm ASM solves the majority of the performance and manageability issues of using low-cost storage to run Oracle on Linux and allows you to build very large, high- performance systems Grant McAlister Principal Database Engineer site.
ACFS provided complete manageability for all customer data. In a continuing fashion, ASM in Oracle Database 12c addresses storage management needs for cloud computing in the enterprise. Cloud computing in the enterprise means applications and their supporting infrastructure are malleable within and across clusters and servers. New features in ASM for Oracle Database 12c enable storage management to seamlessly adapt to changing requirements and configurations.
Furthermore, this evolution brings several new features greatly enhancing management for Oracles engineered systems, such as Exadata and the Oracle Database Appliance. Oracle Flex ASM provides for critical capabilities required for cloud computing in enterprise environments. These environments typically deploy database clusters of varying sizes that not only have stringent performance and reliability requirements, but these environments must be able to rapidly adapt to changing workloads with minimal management overhead.
These ASM instances communicated with other ASM instances on other servers in the cluster and collectively they presented shared Disk Groups to the database clients running in the cluster.
If an ASM instance were to fail, then all the database instances running on the same server as the failing ASM instance failed as well.
The gray boxes in figure 3 represent ASM instances in a prec environment. In Oracle Database release 12c, only a smaller number of ASM instances need run on a subset of servers in a cluster. Furthermore, database instances are connection load balanced across the set of available ASM instances. The default ASM cardinality is 3, but that can be changed with a Clusterware command. There are a reduced number of ASM instances on selected servers in the cluster and Oracle Database 12c clients can connect across the network to ASM instances on different servers.
Furthermore, Oracle Database 12c clients can failover to a surviving server with an ASM instance if a server with an ASM instance fails, all without disruption to the database client. The traffic on the ASM network is usually not overly significant and mostly metadata such as a particular files extent map.
Historically, this approach worked well because the database instances and the ASM instance ran on the same server. With Oracle Database 12c, the database instances and ASM instances can now be on different servers, so ASM instances require a password file that is used to authenticate a database instance connecting to an ASM instance within the cluster.
The ability of storing password files in a Disk Group is extended to Oracle Databases 12c clients. Having a common global password file in a cluster addresses common issues related to synchronizing multiple password files that had to be used previously.
All the instances in an ASM cluster ensure they are running the same code release by validating the patch level across the cluster. The critical capabilities unavailable are associated with prec database clients not being able to access Oracle Flex ASM instances running on remote servers from the server the database instance is running on.
This model offers the most separation between previous database releases and Oracle Database 12c.
See figure 6. Figure 6 The second approach provides for a mixed environment of previous database releases and Oracle Database 12c clients in the same cluster.
In this particular model, both Oracle release 12c and previous databases releases are operated in a cluster with an Oracle 12c ASM instance running on every server in the cluster.
As before, ASM Disk Group compatibility attribute is use for managing the compatibility between database instances. There are two ways to achieve this mixed model of operation. The first is to install the cluster in standard mode which assigns an ASM instance to every server.
The advantage of this approach is that if an Oracle 12c database instance loses connectivity with an ASM instance, then the database connection will failover to another ASM instance on a different server.
See figure 7. The primary objective for administrators is that the ASM instances are up and running. This procedure is one option from several options available to migrate to ASM.
I did choose to test and describe this procedure because it is probably the most efficient and simple available. It will permit the migration databases of all sizes with a minimal downtime window. The level 0 backup is followed by one ore more incremental level 1 backups. The incremental backups are used to keep the level 0 backup in sync with the database until downtime is approved.
When downtime is available we will take the last incremental backup level 1, we will recover the Level 0 backup with it and we will switch the database with the ASM based copy. This procedure does require preparing an empty ASM diskgroup as big as the size of the actual database we will migrate. This procedure consists of 25 steps that can be run from scripts prepared in advance to minimize execution time.
All Rights Reserved. Database dismounted. Block change tracking will help us to fasten the performance of the incremental backup that is part of point 7 of this procedure, if it is not already enabled we will enable it.
In addition we "tag" this backup in order to easily refer to it on the next steps.