The following sections describe Oracle Automatic Storage Management (Oracle ASM) improvements.
See Also:
Oracle Database Testing Guide for details
See Also:
Oracle Database Testing Guide for details
See Also:
Oracle RAC and Grid Infrastructure
1.7.1.1 Oracle Flex ASM
Oracle Flex ASM decouples the Oracle ASM instance from the database servers. Oracle Flex ASM instances may be run on separate physical servers from Oracle Database 12c instances. Any number of Oracle Flex ASM servers can be clustered together to support a large set of databases.
1.7.1.2 Oracle ASM Shared Password File in a Disk Group
This feature implements the infrastructure needed to address the bootstrapping issues of Oracle ASM shared password files in an Oracle ASM disk group. This approach simplifies the administration of password files by ensuring that only a single copy needs to be maintained.
1.7.1.3 Oracle ASM Rebalance Enhancements
Oracle ASM rebalance enhancements improve scalability, performance, and reliability of the rebalance operation. This feature extends the rebalance to operate on multiple disk groups in a single instance. In addition, it improves support for thin provisioning, user data validation, and improved error handling.
With this new feature, you can distribute the rebalance load for higher performance, obtain better user validation, and control error handling and support for thin provisioning.
1.7.1.4 Oracle ASM Disk Resync Enhancements
Oracle ASM disk resync allows multiple disks to be brought online simultaneously or to otherwise control the speed of the resync operation. Oracle ASM disk resync now has a Resync Power Limit to control resync parallelism and, therefore, improve performance. Disk Resync Checkpoint allows for faster recovery from instance failures by allowing the resync to resume from where it was interrupted or stopped instead of starting from the beginning.
This enhancement provides faster recovery from instance failure and faster resync performance overall.
1.7.1.5 Oracle ASM chown, chgrp, chmod and Open Files Support
This feature allows the ASMCMD chown, chgrp, and chmod commands to run even if the affected files are open. In Oracle Database 11g Release 2 (11.2), this was not
See Also:
Oracle Automatic Storage Management Administrator's Guide for
details
See Also:
Oracle Automatic Storage Management Administrator's Guide for
details
See Also:
Oracle Automatic Storage Management Administrator's Guide for
details
See Also:
Oracle Automatic Storage Management Administrator's Guide for
Oracle RAC and Grid Infrastructure
allowed. The ALTER DISKGROUP MODIFY OWNERSHIP SQL command is also similarly modified, as this SQL provides support for these ASMCMD commands.
This feature improves the manageability of Oracle ASM users and the files they own.
1.7.1.6 Oracle ASM Support ALTER DISKGROUP REPLACE USER
This feature introduces a new SQL statement, ALTER DISKGROUP REPLACE USER, that allows the identity of an Oracle ASM user to be changed from one operating system user to another operating system user. This feature allows end users to change the identity of an Oracle ASM user without having to drop and re-create the user, which requires dropping all of the files a user may own.
This feature improves the manageability of Oracle ASM users and the files they own.
1.7.1.7 Enterprise Manager Support for Oracle ASM Features
Enterprise Manager supports the following Oracle ASM features:
■ Oracle Flex ASM server ■ Disk resync improvements
■ Oracle ASM rebalance improvements
■ Enable access control for Oracle ASM files on Windows ■ Oracle ASM corrupt media recovery (scrubbing)
Customers benefit from the easy-to-use interface to monitor and manage these new features like job scheduling, metrics collection, and so on.
1.7.1.8 Oracle ASM File Access Control on Windows
Oracle ASM File Access Control restricts the access of files to specific Oracle ASM clients that connect as SYSDBA. An Oracle ASM client is typically a database which is identified as the user that owns the database instance home.
Beginning with Oracle Database 12c Release 1 (12.1), Oracle supports the use of low-privileged users on Windows instead of Local System Account to run Oracle Database services that let you use separate users for different Oracle databases. This release also supports Oracle ASM disk group file-level access control and privilege separation.
The Oracle ASM File Access Control feature helps to replace the current user with a new user and allows the user to change ownership, group membership, and
permissions of a file while the file is open by one or more Oracle ASM clients. In this release, the low-privileged users for specific Oracle homes are restricted from directly
See Also:
Oracle Automatic Storage Management Administrator's Guide for
details
See Also:
Oracle Automatic Storage Management Administrator's Guide for
details
See Also:
Oracle Automatic Storage Management Administrator's Guide for
Oracle RAC and Grid Infrastructure
accessing Oracle ASM storage devices and can be accessed through the Oracle Database services that have sufficient privileges to run that service.
Oracle ASM disk group users now manage ASM disk group user replacement with new ASMCMD commands and SQL statements.
1.7.1.9 Oracle Grid Infrastructure Rolling Migration for One-Off Patches
Rolling migration framework has been enhanced to handle applying one-off patches released for Oracle ASM in a rolling manner. It also enables migration of a database (Oracle Database 12c Release 1 (12.1) and above) to another Oracle ASM instance to minimize downtime during the course of the rolling migration.
This feature improves database availability by migrating the database to another Oracle ASM instance prior to shut down and upgrade.