| Oracle® Real Application Clusters Installation Guide 11g Release 2 (11.2) for Microsoft Windows Part Number E10818-02 |
|
|
View PDF |
| Oracle® Real Application Clusters Installation Guide 11g Release 2 (11.2) for Microsoft Windows Part Number E10818-02 |
|
|
View PDF |
Most installation errors with Oracle Real Application Clusters (Oracle RAC) are due to a failure to complete all the required steps before starting Oracle Universal Installer (OUI).
This chapter is intended for database administrators to use in consultation with system administrators and storage administrators to coordinate and plan the installation tasks in preparation for completing an installation of Oracle RAC.
This chapter contains the following topics:
This section provides a list of tasks Oracle recommends you complete before starting an Oracle RAC installation. Whether your location is a Tier IV data center with a large project team of system administrators, storage administrators, network administrators, database administrators, and third-party hardware and software vendors, or you are a project team of one, planning is important to help ensure that your installation succeeds.
It is beyond the scope of this documentation set to advise how to determine hardware sizing or capacity planning for your installation. Note that with Oracle Clusterware and Oracle RAC, you can add additional nodes and instances as needed in response to testing, or in response to increased workloads.
Review and complete the following steps as part of your installation plan:
Before you decide whether you want to install Oracle Database 11g release 2 (11.2) on existing hardware, or decide what server and storage hardware to purchase for an installation, log on to My Oracle Support:
Click the More... tab then select Certifications. In the Find Certification Information field, choose the following:
Product Line: Oracle Database Products
Product Family: Oracle Database
Product Area: Oracle Database
Product: Oracle Server - Enterprise Edition
Product Release: 11gR2 RAC
Product Version: 11gR2 RAC
Platform: Microsoft Windows x64 (64-bit)
After you have made these selections, click Search. Click the Certified link next to the value of Platform Version that matches your operating system, for example, Window Server 2008 R2.
Click the link for Certification notes to check the Certification Matrix for Oracle RAC to ensure that your hardware configuration is supported for use with Oracle Clusterware and Oracle RAC. My Oracle Support contains guidance about supported hardware options that can assist you with your purchasing decisions and installation planning.
In addition to specific certified hardware configurations, the Certify page provides support and patch information, and general advice about how to proceed with an Oracle Clusterware with Oracle RAC 11g release 2 (11.2) installation, including important information about configuration issues. View the Product Notes and Platform Notes to view this additional information.
Note:
Contact your Oracle sales representative if you do not have a My Oracle Support account.The Oracle Technical Network (OTN) contains white papers about deployment options, specific implementation scenarios, capacity planning, and extended clusters deployments, which are not addressed in this guide. You can review available papers at the following Web site:
http://www.oracle.com/technology/products/database/clustering/index.html
Installation of Oracle RAC consists of the following steps in order:
Prepare servers (system, storage, and network administrators):
Install operating system and install operating system packages and patches to the required version.
Create required groups, users, and software homes.
Set up domain name forwarding for Grid Naming Service (GNS) if you plan to deploy it, and set up network addresses in the DNS and on the server as needed.
Set up required storage.
(optional) Stage all software on one node for installation (the "local node").
Install Oracle grid infrastructure for a cluster, which includes Oracle Clusterware and Oracle Automatic Storage Management (system and storage administrators):
Install Oracle grid infrastructure for a cluster.
Patch Oracle Clusterware and Oracle Automatic Storage Management to the latest patchset.
Install Oracle RAC (database administrator):
Install Oracle Real Application Clusters.
Patch Oracle RAC to the latest patchset.
Complete postinstallation configuration of the Oracle RAC database.
When installing the Oracle RAC database software, it is faster to install all of the patches for the Oracle Database software before creating a new database than it is to install the patches after you have created a database. For example, after installing the Oracle software, you would patch the Oracle Grid infrastructure home, patch the Oracle Database or Oracle RAC home, and then create the new database.
Oracle provides Cluster Verification Utility to perform system checks in preparation for installation, patch updates, or other system changes.
Cluster Verification Utility is incorporated into Oracle Universal Installer, so it performs its checks when you start the Oracle RAC installation. However, you can use Cluster Verification Utility to ensure that any packages or configuration required for Oracle RAC are in place before you begin your Oracle RAC installation.
Learning how to use Cluster Verification Utility can help system administrators, storage administrators, and database administrators to ensure that each has completed required system configuration and preinstallation steps, so that installations, updates, or patches complete successfully. You can obtain the latest version of Cluster Verification Utility at the following URL:
http://www.oracle.com/technology/products/database/clustering/cvu/cvu_download_homepage.html
If you have a vendor performing hardware or operating system configuration steps for you, then ask the vendor to complete the relevant Cluster Verification Utility check of the cluster after they complete their work to ensure that your system is configured correctly.
Database administrators should refer to the section "Confirming Cluster Readiness for Oracle RAC Installation with CVU" to confirm that their system is prepared for installation before they start an Oracle RAC installation.
If you have an existing Oracle installation, then document version numbers, patches, and other configuration information, and review upgrade procedures for your existing installation. Review Oracle upgrade documentation before proceeding with installation, to decide how you want to proceed.
As with any system change, back up your existing database before attempting to install new software.
Note that to install Oracle RAC 11g release 2 (11.2), you must have Oracle Clusterware and Oracle ASM 11g release 2 (11.2) installed on your cluster. The Oracle Clusterware release version must be equal to or greater than the Oracle RAC version that you want to install.
For the most current information and best practices about pre-upgrade, post-upgrade, compatibility, and interoperability discussions, refer to "Oracle Upgrade Companion." "Oracle Upgrade Companion" is available through Note 785351.1 on My Oracle Support:
For upgrades, note the following:
You can have only one version of Oracle Clusterware running on a cluster at a time. It must be the most recent release of any software (Oracle Clusterware, Oracle Database, Oracle RAC and Oracle Automatic Storage Management) running on the cluster. So, before upgrading your database to Oracle Database 11g release 2, all nodes in the cluster must be upgraded to Oracle Clusterware and Oracle ASM 11g release 2 (11.2).
You can have multiple Oracle homes of Oracle Database software on your cluster. However, the Oracle RAC database software in these homes must be from a version that is equal to or less than the version of Oracle Clusterware that is installed; you cannot use a version of Oracle Database that was released after the version of Oracle Clusterware that you are running.
For example:
If you have Oracle Clusterware 11g release 2 installed as your clusterware, then you can have an Oracle Database 10g release 2 single-instance database running on one node, and separate Oracle RAC 10g release 1, release 2, and Oracle RAC 11g release 1 or release 2 databases also running on the cluster.
You cannot have Oracle Clusterware 10g release 2 installed on your cluster, and install Oracle RAC 11g.
Starting with release 10.1.0.6 and 10.2.0.3, you can use Database Upgrade Assistant (DBUA) for patch set upgrades with Oracle RAC. You can also use DBUA to upgrade between major point releases of Oracle RAC (for example, from 10.2 to 11g, or 11.1 to 11.2).
For the Oracle RAC database being upgraded, DBUA must be run on a node where one of the Oracle RAC database instances is running.
For the Oracle RAC database being upgraded, each cluster member node that hosts an instance of the database must be a member of the upgraded installation. For example, if you have an existing Oracle RAC database running on a three node cluster, then you must upgrade Oracle RAC on all three nodes. You cannot upgrade only 2 nodes of the cluster, removing the third node and instance in the upgrade.
Note:
If you are upgrading an existing Oracle RAC installation, then you must use the same type of Oracle home that you have in your existing installation. For example, if you have a shared Oracle home in your existing installation, then you must upgrade to a shared Oracle home with Oracle RAC 11g release 2 (11.2).Similarly, if you have local Oracle homes on cluster nodes, then you must upgrade to local Oracle homes on cluster nodes.
See Also:
Oracle Database Upgrade Guide for information about how to prepare for upgrading an existing databaseBefore you start an installation where you want to support languages other than English, review Oracle Database Globalization Support Guide.
Note the following:
Oracle recommends that you use Unicode AL32UTF8 as the database character set.
Unicode is the universal character set that supports most of the currently spoken languages of the world. It also supports many historical scripts (alphabets). Unicode is the native encoding of many technologies, including Java, XML, XHTML, ECMAScript, and LDAP. Unicode is ideally suited for databases supporting the Internet and the global economy.
The locale setting of your operating system session determines the language of the user interface, and the globalization behavior for components such as Oracle Universal Installer, Oracle Net Configuration Assistant, and Database Configuration Assistant. It also determines the globalization behavior of Oracle Database sessions created by a user application through Oracle JDBC driver, unless overridden by the application.
The NLS_LANG character set should reflect the setting of the operating system character set of the client. For example, if the database character set is AL32UTF8 and the client is running on a Windows operating system, then you should not set AL32UTF8 as the client character set in the NLS_LANG parameter because there are no UTF-8 WIN32 clients. Instead, the NLS_LANG setting should reflect the code page of the client. For example, on an English Windows client, the code page is 1252. An appropriate setting for NLS_LANG is AMERICAN_AMERICA.WE8MSWIN1252.
Note:
Oracle Database Installation Guide contains a fuller discussion of database character sets used with different languages, and provides further information about installing and configuring Oracle Database globalization support.Users planning to install Oracle Real Application Clusters should review Oracle Grid Infrastructure Installation Guide for Microsoft Windows, particularly the preinstallation and storage chapters, to complete all required steps needed for a successful installation. The Oracle Grid Infrastructure Installation Guide for Microsoft Windows also contains most tasks requiring Administrator user privileges or storage administrator privileges that need to be completed before starting an Oracle RAC installation.
In addition, review the Release Notes and My Oracle Support (https://support.oracle.com) to ensure that you have the most current information about system requirements and other information that can affect your installation. The small time that this review takes can save a much greater amount of time required to track down causes of installation errors later. Also check to make sure that you have the most current version of this document; Oracle Documentation is updated after the initial release and posted to the following Web site:
http://www.oracle.com/pls/db112/homepage
Oracle recommends that you install a Web browser on at least one of your cluster nodes, both to enable Oracle Enterprise Manager and Oracle Application Express for Oracle RAC, and to access online documentation as needed. Online documentation is available in PDF and HTML formats and can be downloaded.
See Also:
Oracle Real Application Clusters Administration and Deployment Guide for additional information about Oracle Clusterware or Oracle RAC configuration and deployment
Oracle Grid Infrastructure Installation Guide for Microsoft Windows contains server and storage configuration information for Oracle RAC
Oracle Clusterware must be installed successfully as part of a grid infrastructure for a cluster installation before attempting to install Oracle RAC.
To complete installations successfully, ensure that required hardware, network, and operating system preinstallation steps for Oracle software are complete. Failure to complete required preinstallation steps is the most common reason for failed installations.
As part of installing Oracle Clusterware, you should already have completed installing and configuring CPUs, memory, shared storage, local disks, network cards, host bus adaptors, interconnects, and any other networking or server hardware; and you should have installed the operating system, and any required packages or third party software. Review your vendor documentation to complete these tasks, and if relevant, work with your vendor to complete the Oracle preinstallation steps that are listed here to confirm that the vendor hardware and software is correctly configured.
During the installation of Oracle grid infrastructure for a cluster, the network administrator, or the person completing the installation, identifies the planned use for each global interface, identifying it as a Public interface type (used with public IP addresses and virtual IP addresses), a Private interface type (used with interconnects between cluster member nodes), or a Do not use interface type, which Oracle Clusterware and Oracle RAC should ignore. For example, an interface used as a dedicated interface for a network file system should be marked as a Do not use interface type.
Additional network configuration is not required during Oracle RAC configuration.
Server preparation for installation include the following:
This section contains a summary of server hardware and software configuration requirements and recommendations.
Required for Oracle RAC
Each node in a cluster requires the following:
Supported server hardware, including processors and system configuration.
Review My Oracle Support before starting installation on your existing hardware and before purchasing new hardware to ensure that the hardware is supported with Oracle Clusterware with Oracle RAC 11g release 2 (11.2).
Also review the preinstallation chapters in Oracle Grid Infrastructure Installation Guide for Microsoft Windows for more details on the supported configurations.
Note:
You must use the same operating system on each node in the cluster. Oracle strongly recommends that you use the same software configurations on each node of the cluster. Oracle Clusterware and Oracle RAC do not support heterogeneous platforms (servers that have different chip architectures) in the same cluster.Operating system updates listed in the system requirements.
Oracle may require updates to the operating system, such as Service Packs and individual patches. If such requirements exist, then they will be stated in the Release Notes for a particular release. You can also apply other operating system patches as recommended by Microsoft, provided that there are no "certification exceptions" listed in the Release Notes.
A supported interconnect software protocol on each node, to support Oracle Clusterware voting disk polling, and to support Cache Fusion in Oracle RAC. Your interconnect must be certified by Oracle for your platform.
Recommended for Oracle RAC: System Administrator Tasks
Oracle recommends the following tasks to simplify server installation and maintenance, and to prevent service issues:
Utilizing a time protocol, such as Network Time Protocol (NTP), to ensure that all nodes in the cluster use the same reference time. With Oracle Clusterware 11g release 2 (11.2), if the network time protocol is not enabled when Oracle Clusterware is started, then the cluster time synchronization service (CTSS) is enabled.
Configuring redundant switches, for all cluster sizes.
Using identical server hardware on each node, to simplify server maintenance.
Avoiding resource contention issues by not installing Oracle RAC on a primary domain controller or backup domain controller.
Additional Options: System Administrators and Vendors
After you have set up server hardware, review "Checking the Hardware Requirements" in the Oracle Grid Infrastructure Installation Guide for Microsoft Windows to ensure that your system has enough RAM, that the TEMP environment variable points to a location that has enough available space for the installation, and that your system meets other hardware requirements.
Configure the users and user environments as described in the preinstallation chapters of the Oracle Grid Infrastructure Installation Guide for Microsoft Windows. These include the following tasks:
Creating operating system users to install Oracle software.
Configuring the Oracle software owner user environments.
See Also:
Oracle Database Platform Guide for Microsoft Windows for information about creating user groupsTo install the Oracle software, you must use a user that is a member of the Administrators group. If you use a local user account for the installation, then the user account must exist on all nodes in the cluster and the user name and password must be the same on all nodes.
If you use a domain account for the installation, then the domain user must be explicitly declared as a member of the local Administrators group on each node in the cluster. It is not sufficient if the domain user has inherited membership from another group. The user performing the installation must be in the same domain on each node. For example, you cannot have a dba1 user on the first node in the DBADMIN domain and a dba1 user on the second node in the RACDBA domain.
For example, assume that you have one Oracle installation owner, and the user name for this Oracle installation owner is oracle. The oracle user must be either a local Administrator user or a domain user, and the same user must exist (same user name, password, and domain) on each node in the cluster.
When installing the Oracle Database software, the user performing the installation is automatically added to the ORA_DBA group. If you use a domain user, then you must make sure the domain user on each node is a member of local Administrator group and the ORA_DBA group.
Members of the local ORA_DBA group automatically receive the SYSDBA and SYSASM privileges.
Note:
If you use a domain user to perform the installation, then in some cases you must manually add the user to
ORA_DBA group of the remote nodes after installation completes.See Also:
Oracle Database Installation Guide for Microsoft Windows for more information about theORA_DBA groupThe Oracle base directory is the location where Oracle software and configuration files are stored. By default, the Oracle software binary files are installed by version and Oracle home name in a subdirectory of the Oracle base directory.
During installation, you are prompted for the Oracle base path. Each operating system user that performs an installation of Oracle software should have their own Oracle base directory. An Oracle base directory can be used for more than one installation. You are also prompted for a software location, or the Oracle home, for this software installation.
Oracle Universal Installer (OUI) creates other paths and environment variables as necessary, in accordance with the Optimal Flexible Architecture (OFA) rules for well-structured Oracle software environments. If you install an OFA-compliant database using Oracle Universal Installer defaults, then ORACLE_BASE is X:\app\user_name\ (for example, C:\app\oracle), where X is any hard drive, and user_name is the name of the user performing the installation.
With Oracle Database 11g, Oracle recommends that you do not set an Oracle home environment variable prior to installation, and instead allow OUI to create the Oracle home directory. If the Oracle base path is C:\app\oracle, then by default, OUI creates the following Oracle home path:
C:\app\oracle\product\11.2.0\dbhome_n
where n is the Oracle home number. For example, the first time you create an Oracle home as the oracle user, the default Oracle home location is C:\app\oracle\product\11.2.0\dbhome_1.
Ensure that the paths you select for Oracle software, such as Oracle home paths and the Oracle base path, use only ASCII characters. Because installation owner names are used by default for some paths, this ASCII character restriction applies to user names, file names, and directory names.
The Oracle software is installed on one node in the cluster and then the installer copies the software to the other nodes in the cluster. You should verify that each node in your cluster can communicate with the other nodes using the net use command, for example:
C:\> net use \\node2\c$ The command completed successfully.
On node 2, you would use the following command:
C:\> net use \\node1\c$ The command completed successfully.
You need a web browser to access documentation, to use Oracle Enterprise Manager and to use Oracle Application Express. Web browsers must support Java Script and the HTML 4.0 and CSS 1.0 standards. The following browsers meet these requirements:
Netscape Navigator 7.2
Netscape Navigator 8.1
Mozilla version 1.7
Microsoft Internet Explorer 6.0 SP2
Microsoft Internet Explorer 7.0 or later
Firefox 3.0
Firefox 3.5
Oracle Clusterware and Oracle RAC are tested with specific operating system versions, and specific operating system components. Oracle requires that you use the operating system versions and components that are certified for this release.
Oracle recommends that you or your system administrator review the system requirements carefully in Oracle Grid Infrastructure Installation Guide for Microsoft Windows before beginning installation, to ensure that your system meets these requirements. If your system does not meet minimum hardware, operating system version and component requirements, then your installation may fail to complete, or other errors may develop during Oracle Clusterware or Oracle Database runtime.
In addition to the standard system requirements configuration, deployment on specific server hardware can include additional operating system configuration steps. Review the Preinstallation chapters in Oracle Grid Infrastructure Installation Guide for Microsoft Windows, and check the My Oracle Support Certify page to ensure that you are aware of any additional requirements or recommendations for your specific hardware and platform configuration.
For both the Enterprise and Standard Editions of Oracle RAC, the hard disk requirements for Oracle Database components include 32 MB required to install Java Runtime Environment (JRE) and OUI on the partition where the operating system is installed. If sufficient space is not detected, then the installation fails and an error message appears. Table 1-1 lists the hard disk space requirements, including the requirement for the starter database.
Table 1-1 Hard Disk Space Requirements for Oracle RAC
| Installation Type | TEMP space | SYSTEM_DRIVE:\Program Files\Oracle | Oracle Database Home | Data FilesFoot 1 | Total |
|---|---|---|---|---|---|
|
Standard Edition |
500 MB |
100 MB |
5 GB |
3 GBFoot 2 |
8.6 GB |
|
Enterprise Edition |
500 MB |
100 MB |
5.5 GB |
3 GB |
9.1 GB |
Footnote 1 Refers to the contents of the admin, flash_recovery_area, and oradata directories in the ORACLE_BASE directory
Footnote 2 This size can be greater, depending on the installation options selected, such as languages or additional components. If you later plan to install Oracle Database and Oracle Real Application Clusters with automated backups enabled, then include at least an additional 2 GB for data file disk space.
To install Oracle RAC, you need to have configured shared storage for the database files and optionally the recovery files. If you instruct Database Configuration Assistant (DBCA) to configure automatic backups, the backups require a database recovery area that must be shared.
Refer to the chapter "Configuring Oracle Real Application Clusters Storage" in Oracle Grid Infrastructure Installation Guide for Microsoft Windows to review storage options for installation planning. Storage and system administrators can refer to this chapter to configure storage for database files for an Oracle RAC database.
See Also:
Oracle Database Administrator's Guide for information about recovery areasOracle Automatic Storage Management Cluster File System (Oracle ACFS) is a new multi-platform, scalable file system, and storage management technology that extends Oracle Automatic Storage Management (Oracle ASM) functionality to support customer files maintained outside of the Oracle Database. Files supported by Oracle ACFS include database and application executables, trace files, alert logs, application reports, BFILEs, and configuration files. Oracle ACFS leverages Oracle ASM functionality that enables Oracle ACFS dynamic file system resizing, maximized performance through direct access to Oracle ASM disk group storage, balanced distribution of Oracle ACFS across Oracle ASM disk group storage for increased I/O parallelism, and data reliability through Oracle ASM mirroring protection mechanisms.
The Oracle ASM Dynamic Volume Manager (Oracle ADVM) provides volume management services and a standard disk device driver interface to clients. 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. Oracle ADVM extends Oracle ASM by providing a disk driver interface to Oracle ASM storage allocated as Oracle ASM volume files. You can use the Dynamic Volume Manager to create virtual disks that contain file systems. These 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.
See Also :
The Certify page on My Oracle Support for the most current information about storage options:
https://support.oracle.com
Oracle Database Storage Administrator's Guide for an overview of storage configuration administration
For all installations, you must choose the storage option that you want to use for Oracle Real Application Clusters (Oracle RAC) database files. If you want to enable automated backups during the installation, then you must also choose the shared storage option that you want to use for recovery files (the fast recovery area). You do not have to use the same storage option for each file type.
Use the following guidelines when choosing the storage options that you want to use for each file type:
You can choose any combination of the supported shared storage options for each file type provided that you satisfy all requirements listed for the chosen storage options.
Oracle recommends that you choose Oracle Automatic Storage Management (Oracle ASM) as the shared storage option for database and recovery files.
For Standard Edition Oracle RAC installations, Oracle ASM is the only supported shared storage option for database or recovery files.
If you do not have a storage option that provides external file redundancy, then you must configure at least three voting disk areas to provide voting disk redundancy.
If you intend to use Oracle ASM with Oracle RAC and you did not use Oracle ASM for the Oracle Clusterware files (OCR and voting disk), then you must configure the Oracle ASM instance with ASMCA before starting Oracle Universal Installer (OUI). All nodes in the cluster must have the Oracle Database 11g release 2 version of the grid infrastructure installed (Oracle Clusterware and Oracle ASM).
If you intend to upgrade an existing Oracle RAC database, then you must ensure that your system meets the following conditions:
Oracle Universal Installer (OUI) and Database Configuration Assistant (DBCA) are run on the node where the Oracle RAC database instance is located.
The Oracle RAC database instance is running on the same nodes that you intend to make members of the new cluster installation. For example, if you have an existing Oracle RAC database running on a three-node cluster, then you must install the upgrade on all three nodes. You cannot upgrade only 2 nodes of the cluster, removing the third instance in the upgrade.
See Also:
Oracle Database Upgrade Guide for information about how to prepare for upgrading an existing databaseThere are three ways of storing Oracle Database and recovery files:
Note:
Installing on raw devices (unformatted partitions) is not supported. Install on a shared file system or on Oracle ASM. If you are upgrading a database that uses raw devices, they are still supported with Oracle Database 11g release 2.Oracle Automatic Storage Management: Oracle Automatic Storage Management (Oracle ASM) is an integrated, high-performance database file system and disk manager for Oracle Database files. It performs striping and mirroring of database files automatically.
A supported shared file system: Supported file systems include the following:
Oracle Cluster File System (OCFS) for Windows: Note that if you intend to use OCFS for Windows for your database files, then you should create partitions large enough for the all the database and recovery files when you create partitions for use by Oracle Database.
Note:
If you want to have a shared Oracle Database home directory for all nodes, then you must use OCFS for Windows.Direct Network File Systems (NFS): You can configure Oracle Database to access NFS V3 servers directly using an Oracle internal Direct NFS client.
Table 1-2 shows the storage options supported for storing Oracle Database files and Oracle Database recovery files. Oracle Database files include data files, control files, redo log files, the server parameter file, and the password file.
Table 1-2 Supported Storage Options for Oracle Database and Recovery Files
| Storage Option | File Types Supported | |
|---|---|---|
| Database | Recovery | |
|
Oracle ASM |
Yes |
Yes |
|
Oracle ASM Cluster File System (Oracle ACFS) |
No |
No |
|
OCFS for Windows |
Yes |
Yes |
|
Direct NFS |
Yes |
Yes |
|
Local storage |
No |
No |
|
Shared unformatted partitions |
Not supported by OUI or ASMCA, but supported by the software. They can be added or removed after installation. |
Not supported by OUI or ASMCA, but supported by the software. They can be added or removed after installation. |
This section contains additional information about Oracle Clusterware, Oracle ASM, and Oracle RAC, that may be helpful for your installation planning team in deciding how you want to configure your installation. It contains the following sections:
In past releases, Oracle ASM was installed as part of the Oracle Database installation. With Oracle Database 11g release 2 (11.2), Oracle ASM is part of an Oracle grid infrastructure installation. If you want to upgrade an existing Oracle ASM installation, then you must upgrade Oracle ASM by running an Oracle grid infrastructure upgrade.
For Oracle RAC, you and your system administrator should note that all instances in Oracle RAC environments share the control file, server parameter file, redo log files, and all data files. These files must be placed on a shared file systems, and all the cluster database instances must have access to them. Each instance also has its own set of redo log files. During failures, shared access to redo log files enables surviving instances to perform recovery.
As part of installation of Oracle Database 11g release 2 (11.2), time zone version files from 1 to 11 are installed in the path Oracle_home\oracore\zoneinfo. You can continue to use the current time zone version or upgrade to the latest version. Oracle recommends that you upgrade the server to the latest timezone version. Upgrading to a new timezone version may cause existing TIMESTAMP WITH TIME ZONE (TSTZ) data to become stale. Using the newly provided DBMS_DST PL/SQL packages, you can update the TSTZ data transparently with minimal manual procedures and system downtime.
Time zone version files are also installed on the clients. Starting with Oracle Database 11g release 2, you no longer need to upgrade Oracle Client time zone files immediately. Upgrades can be done at a time when it is most convenient to the system administrator. However, there could be a small performance penalty when client and server use different time zone versions.
See Also:
Oracle Database Upgrade Guide for information about preparing to upgrade Timestamp with Time Zone data
Oracle Database Globalization Support Guide for information about how to upgrade the Time Zone file and Timestamp with Time Zone data
Oracle Call Interface Programmer's Guide for information about performance effects of clients and servers operating with different versions of Time Zone files
You can install and operate different releases of Oracle Database software on the same computer when the following conditions are met:
If you have Oracle Clusterware installed and different release versions of other Oracle software installed, then the Oracle Clusterware version must be greater than or equal to the Oracle Database software version. Oracle Clusterware and Oracle Automatic Storage Management are both upgraded with an Oracle grid infrastructure 11g release 2 (11.2) installation.
If you have an existing Oracle Database home, then you can create a new Oracle Database home and install Oracle Database 11g release 2 (11.2) into the new Oracle home. You should ensure that Oracle Clusterware is in a separate grid infrastructure home. Oracle grid infrastructure for a cluster installations cannot be installed in the Oracle base directory for Oracle Database.
If you are running Oracle9i Database software, and you want to continue to use that release, then you must run cluster software that is compatible with that release, such as Oracle Cluster Manager. Oracle Clusterware release 11g can be installed on the same system as Oracle9i Database software, but Oracle9i Database software cannot be supported by Oracle Clusterware 11g.
See Also:
Oracle Grid Infrastructure Installation Guide for Microsoft Windows for information about using older Oracle Database versions with grid infrastructure
"Installing Oracle 11g Database on a System with Oracle9i Database Release 2"
If you select the Upgrade an existing database option in OUI, then, after you have completed the installation interview, the database upgrade assistant (DBUA) is started to upgrade the database. The information collected during the installation interview is passed to DBUA after the software is installed.
If OUI detects a previous Oracle Clusterware release, then you are asked to upgrade the existing Oracle Clusterware installation. You can run only one Oracle Clusterware version on a server, and a server must be a member of only one cluster. Oracle Clusterware must be at the same or a higher release than the Oracle Database software for Oracle RAC.
You cannot install Oracle grid infrastructure for a standalone server (Oracle Restart) and then install Oracle grid infrastructure for a cluster. If you have Oracle grid infrastructure for a standalone server (Oracle Restart) installed, then you must remove that installation before you can install Oracle grid infrastructure for a cluster.
Note:
Do not move Oracle executables from the directory in which they were installed to another location. To move the executable files to a new location, you must reinstall the software.You can run different releases of Oracle Database and Oracle Automatic Storage Management (Oracle ASM). For example, you can use Oracle ASM release 11g release 2 (11.2) with an Oracle Database 10g release 2 (10.2) database
Note:
When using different release Oracle ASM and Oracle Database releases, the functionality of each is dependent on the functionality of the earlier software release. For example, an Oracle Database 10g release 10.2 database using an Oracle ASM 11g release 2 (11.2) instance will not be able to use new features available for Oracle ASM in the 11g release 2 (11.2) release, but instead only Oracle ASM 10.2 features.Before you start your installation, use Cluster Verification Utility (CVU) to ensure that your system is prepared for installing Oracle RAC. If any checks fail, then fix the errors reported, either manually or by using a generated fixup script, or contact your system or storage administrator to have the cause of the errors addressed.
CVU is available in the Grid home, in the bin directory. For example, if the Oracle grid infrastructure for a cluster home is C:\app\11.2.0\grid, then the path is C:\app\11.2.0\grid\bin. To start CVU, navigate to the Grid home bin directory, and use a command similar to the following:
cluvfy.bat stage -pre dbinst -fixup -n nodelist -r release -verbose
In the preceding command, nodelist is a comma-delimited list of node names and release is the version of the Oracle Database software being installed. The -fixup and-verbose flags are optional.
For example, for a two node cluster with node1 and node2, where you are testing the cluster to prepare to install Oracle Database 11g release 2 (11.2) with Oracle RAC, the following command checks for system readiness:
cluvfy.bat stage -pre dbinst -fixup -n node1,node2 -r 11gR2 -verbose
For more information about CVU commands, run the command cluvfy.bat -help.
See Also:
Oracle Clusterware Administration and Deployment Guide for detailed information about CVUIf you are planning an installation on a system where you have an existing Oracle RAC or Oracle Database installation, then you must perform additional tasks to prepare your system for installation.
Table 1-3 provides an overview of what you need to do if you have an existing Oracle Database installation. Review the table, and perform tasks as required.
See Also:
Oracle Database Upgrade Guide for additional information about preparing for and performing upgradesTable 1-3 Overview of System Preparation for Upgrades or Co-existing Databases
| Installation Scenario | What you need to do |
|---|---|
|
Upgrading from Oracle Database 10g release 1 (10.1) to Oracle Database 11g release 2 (11.2) |
No additional tasks. Refer to "Installing Oracle Database 11g on a System with Oracle Database 10g" |
|
Installing Oracle Database 11g release 2 (11.2) on a system to coexist with Oracle Database 10g release 1 (10.1) |
No additional tasks. Refer to "Installing Oracle Database 11g on a System with Oracle Database 10g" |
|
Upgrading from Oracle9i release 9.2 to Oracle Database 11g release 2 (11.2) |
Shut down the Global Service Daemon, and shut down a default listener on port 1521, if present. Refer to "Installing Oracle 11g Database on a System with Oracle9i Database Release 2" |
|
Installing Oracle Database 11g release 2 (11.2) on a system to co-exist with Oracle9i release 9.2 |
Shut down a default listener on port 1521, if present, and shut down the Global Service Daemon. Refer to "Installing Oracle 11g Database on a System with Oracle9i Database Release 2" |
If your system has an Oracle Database 10g installation, and you install Oracle Database 11g release 2 (11.2) either to coexist with or to upgrade the Oracle Database 10g installation, then most installation types configure and start a default Oracle Net listener using TCP/IP port 1521 and the IPC key value EXTPROC. One of the following occurs:
During a co-existing installation, Database Configuration Assistant (DBCA) automatically migrates the listener and related files from the Oracle Database 10g Oracle home to the Oracle Database 11g Oracle home.
During an upgrade, Oracle Database Upgrade Assistant (DBUA) automatically locates the Oracle Database10g listener, and migrates it to Oracle Database 11g.
If you are installing an Oracle Database 11g release 2 (11.2) on a system with an existing Oracle9i Database release 2 (9.2), and the Oracle Net listener process is using the same port or key value as the default used with the Oracle Database 11g release 2 (11.2) installation, port 1521, then OUI can only configure the new listener; it cannot start it. To ensure that the new listener process starts during the installation, you must shut down any existing listeners before starting OUI. To do this, refer to "Shutting Down the Listener"
You must shut down the Global Services Daemon (GSD), because otherwise, during Oracle Database 11g installation, the Oracle Database 9i release 2 (9.2) SRVM shared data is upgraded into an Oracle Cluster Registry that the Oracle9i release 2 GSD will not be able to use. The Oracle grid infrastructure installation starts an 11g release 2 (11.2) GSD to serve the Oracle9i release 2 (9.2) clients. To do this, refer to "Shutting down the Global Services Daemon".
Note:
To run an Oracle 9i RAC database, you must have the Oracle 9i Cluster Manager operational. It can run on the same server with an Oracle Grid Infrastructure installation. Oracle Clusterware does not manage Oracle9i RAC databases.Shutting Down the Listener To determine if an existing Oracle Database 9i listener process is running and to shut it down if necessary, follow these steps:
Open the Services management interface:
On Windows Server 2003 and Windows Server 2003 R2, from the Start menu, select Administrative Tools, and then select Services.
On Windows Server 2008 and Windows Server 2008 R2, from the Start menu, select Server Manager. In the Server Manager console, expand Diagnostics and then select Services.
Locate any services with a name similar to OracleOraDb9i_homeTNSListener.
Select the service name. In the Action menu, click Stop.
Shutting down the Global Services Daemon On each node of the cluster, use the following syntax to shut down the GSD:
C:\> cd 92_oracle_home\bin
C:\> gsdctl stop
In the preceding syntax example, the variable 92_Oracle_home is the Oracle Database 9i release 2 (9.2) home.
|
 Copyright © 2007, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|