| Oracle® Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Microsoft Windows Part Number E10817-01 |
|
|
View PDF |
| Oracle® Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Microsoft Windows Part Number E10817-01 |
|
|
View PDF |
This section describes new features as they pertain to the installation and configuration of Oracle Grid Infrastructure (Oracle Clusterware and Oracle Automatic Storage Management), and Oracle Real Application Clusters (Oracle RAC). The topics in this section are:
The following is a list of options desupported with this release:
With this release, OUI no longer supports installation of Oracle Clusterware files on raw devices. Install Oracle Clusterware files either on Oracle Automatic Storage Management diskgroups, or in a supported shared file system.
Raw devices are still supported for systems upgrading to Oracle Clusterware 11g release 2.
The following is a list of new features for Oracle Database 11g release 2 (11.2):
Oracle Automatic Storage Management and Oracle Clusterware Installation
Oracle Automatic Storage Management and Oracle Clusterware Files
Oracle Automatic Storage Management Cluster File System (Oracle ACFS)
Daylight Savings Time Upgrade of Timestamp with Timezone Data Type
Oracle Clusterware Administration with Oracle Enterprise Manager
With Oracle Grid Infrastructure 11g release 2 (11.2), Oracle Automatic Storage Management (Oracle ASM) and Oracle Clusterware are installed into a single home directory, which is referred to as the Grid Infrastructure home. Configuration assistants start after the installer interview process that configure Oracle ASM and Oracle Clusterware.
The installation of the combined products is called Oracle Grid Infrastructure. However, Oracle Clusterware and Oracle Automatic Storage Management remain separate products.
With this release, Oracle Cluster Registry (OCR) and voting disks can be placed on Oracle Automatic Storage Management (Oracle ASM).
This feature enables Oracle ASM to provide a unified storage solution, storing all the data for the clusterware and the database, without the need for third-party volume managers or cluster filesystems.
For new installations, OCR and voting disk files can be placed either on Oracle ASM, or on a cluster file system. Installing Oracle Clusterware files on raw devices is no longer supported, unless an existing Oracle Clusterware 10g release 1 or higher system is being upgraded.
Oracle Automatic Storage Management Cluster File System (Oracle ACFS) is a new multi-platform, scalable file system and storage management design that extends Oracle Automatic Storage Management (Oracle ASM) technology to support all application data. Oracle ACFS provides dynamic file system resizing, and improved performance using the distribution, balancing and striping technology across all available disks, and provides storage reliability through Oracle ASM's mirroring and parity protection.
Note:
Oracle ACFS is only supported on Windows Server 2003 64-bit and Windows Server 2003 R2 64-bit.The Oracle ASM Dynamic Volume Manager (Oracle ADVM) extends Oracle ASM by providing a disk driver interface to Oracle ASM storage allocated as Oracle ASM volume files. You can use Oracle ADVM to create virtual disks that contain file systems. File systems and other disk-based applications issue I/O requests to Oracle ADVM volume devices as they would to other storage devices on a vendor operating system. The file systems contained on Oracle ASM volumes can be used to support files beyond Oracle database files, such as executable files, report files, trace files, alert logs, and other application data files.
Cluster node times should be synchronized, particularly if the cluster is to be used for Oracle Real Application Clusters. With this release, Oracle Clusterware provides Cluster Time Synchronization Service (CTSS), which ensures that there is a synchronization service in the cluster. If Network Time Protocol (NTP) is not found during cluster configuration, then CTSS is configured to ensure time synchronization.
When time zone version files are updated, TIMESTAMP WITH TIMEZONE data could become stale. With timestamp automation, the system and user data is updated transparently with minimal downtime. In addition, clients can continue to work with the server without having to update the client-side files.
Enterprise Manager Database Control 11g provides the capability to automatically provision Oracle Grid Infrastructure and Oracle RAC installations on new nodes, and then extend the existing Oracle Grid Infrastructure and Oracle RAC database to these provisioned nodes. This provisioning procedure requires a successful Oracle RAC installation before you can use this feature.
See Also:
Oracle Real Application Clusters Administration and Deployment Guide for information about this featureWith this release, you can install a new version of Oracle Clusterware into a separate home from an existing Oracle Clusterware installation. This feature reduces the downtime required to upgrade a node in the cluster. When performing an out-of-place upgrade, the old and new version of the software are present on the nodes at the same time, each in a different home location, but only one version of the software is active.
In the past, adding or removing servers in a cluster required extensive manual preparation. With this release, you can continue to configure server nodes manually, or use Grid Plug and Play to configure them dynamically as nodes are added or removed from the cluster.
Grid Plug and Play reduces the costs of installing, configuring, and managing server nodes by starting a grid naming service within the cluster to allow each node to perform the following tasks dynamically:
Negotiating appropriate network identities for itself
Acquiring additional information it needs to operate from a configuration profile
Configuring or reconfiguring itself using profile data, making host names and addresses resolvable on the network
Because servers perform these tasks dynamically, adding and removing nodes simply requires an administrator to connect the server to the cluster and allow the cluster to configure the node. Using Grid Plug and Play, and using best practices recommendations, adding a node to the database cluster is part of the normal server restart, and removing a node from the cluster occurs automatically when a server is turned off.
With this release, you can use Enterprise Manager Cluster Home page to perform full administrative and monitoring support for both standalone database and Oracle RAC environments, using High Availability Application and Oracle Cluster Resource Management.
When Oracle Enterprise Manager is installed with Oracle Clusterware, it can provide a set of users that have the Oracle Clusterware Administrator role in Enterprise Manager, and provide full administrative and monitoring support for High Availability application and Clusterware resource management.
After you have completed installation and have Enterprise Manager deployed, you can provision additional nodes added to the cluster using Enterprise Manager.
With this release, Oracle Clusterware can use redundant network interfaces for the Clusterware interconnect, without requiring external or operating system-based bonding solutions. This provides the following advantages:
High availability for the cluster by removing the network interface as a single point of failure
Dynamic load-balancing across all available NICs
Ability to add or replace private interfaces during runtime; Oracle Clusterware automatically recognizes and aggregates new or replaced interfaces to private interconnect addresses
Support for UDP, TCP and raw interfaces
With this release, the single client access name (SCAN) is the address to provide for all clients connecting to the cluster. The SCAN is a domain name registered to at least one and up to three IP addresses, either in the domain name service (DNS) or the Grid Naming Service (GNS). The SCAN eliminates the need to change clients when nodes are added to or removed from the cluster. Clients using SCAN can also access the cluster using Easy Connect Naming.
With this release, you can use srvctl to shut down all Oracle software running within an Oracle home, in preparation for patching. Oracle Grid Infrastructure patching is automated across all nodes, and patches can be applied in a multi-node, multi-patch fashion.
To streamline cluster installations, especially for those customers who are new to clustering, Oracle introduces the Typical Installation path. Typical installation provides defaults for as many options as possible to those recommended as best practices.
Oracle Universal Installer no longer removes Oracle software. Use the new Deinstallation Tool (deinstall.bat) available on the installation media before installation as well as in the Oracle home directory after installation. This tool can also be downloaded from Oracle TechNet.
See Also:
Chapter 6, "How to Modify or Deinstall Oracle Grid Infrastructure" for more informationIn prior releases, backing up the voting disks was a required postinstallation task. With Oracle Clusterware release 11.2 and later, backing up voting disks manually is no longer required, as voting disks are backed up automatically in the OCR as part of any configuration change and voting disk data is automatically restored to any added voting disks.
The following is a list of new features for release 1 (11.1)
With Oracle Database 11g release 1, Oracle Clusterware can be installed or configured as an independent product, and additional documentation is provided on storage administration. For installation planning, note the following documentation:
This book provides an overview and examples of the procedures to install and configure a two-node Oracle Clusterware and Oracle RAC environment.
This book (the guide that you are reading) provides procedures either to install Oracle Clusterware as a standalone product, or to install Oracle Clusterware with either Oracle Database, or Oracle RAC. It contains system configuration instructions that require system administrator privileges.
This platform-specific book provides procedures to install Oracle RAC after you have successfully completed an Oracle Clusterware installation. It contains database configuration instructions for database administrators.
This book provides information for database and storage administrators who administer and manage storage, or who configure and administer Oracle Automatic Storage Management (Oracle ASM).
This is the administrator's reference for Oracle Clusterware. It contains information about administrative tasks, including those that involve changes to operating system configurations and cloning Oracle Clusterware.
This is the administrator's reference for Oracle RAC. It contains information about administrative tasks. These tasks include database cloning, node addition and deletion, Oracle Cluster Registry (OCR) administration, use of SRVCTL and other database administration utilities, and tuning changes to operating system configurations.
The following is a list of enhancements and new features for Oracle Database 11g release 1 (11.1):
This feature introduces a new SYSASM privilege that is specifically intended for performing Oracle ASM administration tasks. Using the SYSASM privilege when connecting to Oracle ASM instead of the SYSDBA privilege provides a clearer division of responsibility between Oracle ASM administration and database administration.
|
 Copyright © 2007, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
