1 Preinstallation Checklist

Most installation errors with Oracle Real Application Clusters (Oracle RAC) are due to a failure to complete all steps required before starting Oracle Universal Installer.

This chapter is intended for database administrators to use in consultation with system administrators and storage administrators to coordinate installation plan tasks for Oracle Clusterware, in preparation for completing an installation of Oracle RAC.

This chapter contains the following topics:

1.1 Before You Start: Planning your Installation

This section provides a list of tasks Oracle recommends you complete before starting Oracle Clusterware and 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 proceeds smoothly.

It is beyond the scope of this documentation set o 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:

1.1.1 Check OracleMetaLink

Before you decide whether you want to install Oracle Database 11g release 1 (11.1) on existing hardware, or decide what server and storage hardware to purchase for an installation, log on to OracleMetaLink (https://metalink.oracle.com), and click the Certify tab. Check the Certification Matrix for Oracle RAC for the operating system platform on which you intend to install, to ensure that your hardware configuration is supported for use with Oracle Clusterware, and, if you intend to install it, Oracle RAC. You can receive guidance about supported hardware options that can assist you with your purchasing decisions.

At the time of this release, you can also check the following URL for direct access to the Certification Matrix:

http://www.oracle.com/technology/support/metalink/index.html

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 or Oracle Clusterware with Oracle RAC 11g release 1 (11.1) installation, including important information about vendor clusterware and other configuration issues.

Contact your Oracle Sales Representative if you do not have an OracleMetaLink account.

Also, you may want to refer to Oracle.com (http://www.oracle.com) for additional resources about planning for specific implementation scenarios, best practices, and other information that can help you with your installation plan. In particular, refer to the following Web site:

http://www.oracle.com/technology/products/database/clustering/index.html

1.1.2 Check Oracle Technical Network

The Oracle Technical Network (OTN) contains white papers about deployment options, such as capacity planning, best practices on various NFS platforms, 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

1.1.3 Review How to Use Cluster Verification Utility

All users intending to install Oracle Clusterware or Oracle RAC should use Cluster Verification Utility to ensure that the cluster is prepared for a successful installation.

Oracle provides Cluster Verification Utility to perform system checks in preparation for installation, patch updates, or other system changes. 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.

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.

1.1.4 Review and Back Up Existing Oracle Installations

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.

For late-breaking updates and best practices about preupgrade, post-upgrade, compatibility, and interoperability discussions, refer to "Oracle Upgrade Companion." "Oracle Upgrade Companion" is available through Note 466181.1 on OracleMetaLink:

https://metalink.oracle.com/

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 Automatic Storage Management) running on the cluster.

  • You can have multiple Oracle homes of Oracle Database 11g release 1 (11.1) or later 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 have a version of Oracle Database on Oracle Clusterware that was released after the version of Oracle Clusterware that you are running.

    For example:

    If you have Oracle Clusterware 11g release 1 installed as your clusterware, then you can have an Oracle Database 10g release 1 single-instance database running on one node, and separate Oracle RAC 10g release 1, release 2, and Oracle RAC 11g release 1 databases also running on the cluster.

    However, you cannot have Oracle Clusterware 10g release 2 installed on your cluster, and install Oracle RAC 11g.

  • You can install earlier or later versions of Automatic Storage Management, but you can have only one ASM installation running in the cluster.

    Both forward and backward compatibility is available with different versions of Automatic Storage Management (ASM). However, if you mix software versions, then be aware that ASM functionality reverts to the earliest software installation it supports.

    For example, if you install Oracle Clusterware 11g with ASM, and you use it to support an existing Oracle Database release 10.2.0.3 installation, then ASM functionality is equivalent only to that available in the 10.2 release version.

  • 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.1 to 10.2, or 10.2 to 11g).

  • If you want to upgrade Oracle Clusterware release 10.2 to Oracle Clusterware release 11g, then you must first apply the 10.2.0.3 or later patch set.

  • You cannot change the owner of the Oracle ASM or Oracle Database home during an upgrade. You must use the same Oracle software owner that owns the existing Oracle ASM or Oracle Database home.

  • As with any system change, back up your existing database before attempting to install new software.

See Also:

Oracle Database Upgrade Guide

1.1.5 Review Globalization Requirements

Before 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 environment variable determines the language of the user interface and the globalization behavior for components such as SQL*Plus, exp, and imp. It sets the language and territory used by the client application and the database. It also declares the character set for entering and displaying data by the client application.

Note:

Oracle Database Installation Guide for your platform contains a fuller discussion of database character sets used with different languages, and provides further information about installing and configuring Oracle Database globalization support.

1.1.6 Review Documentation

Users planning to install Oracle Clusterware should review Oracle Clusterware Installation Guide for your operating system platform, particularly the Preinstallation, and the Storage chapters, to complete all required steps needed for a successful installation.

Oracle Clusterware Installation Guide also contains most tasks requiring root privileges or storage administrator privileges that need to be completed before starting an Oracle RAC installation.

In addition, review the Release Notes and OracleMetalink (https://metalink.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.

Oracle recommends that you install a Web browser on your cluster nodes, both to enable Oracle Enterprise Manager and Oracle Application Express, if you install Oracle RAC, and to access online documentation as needed. Online documentation is available in PDF and HTML formats.

Note:

Refer to Oracle Database Concepts for an overview of Oracle Database, and Oracle Real Application Clusters Administration and Deployment Guide for additional information about Oracle Clusterware or Oracle RAC configuration and deployment. The Oracle Clusterware Installation Guide for your platform contains server and storage configuration information for Oracle RAC.

1.2 Server Hardware, Network and Operating System Overview

Oracle Clusterware must be installed successfully 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.

Before Oracle Clusterware is installed, you should already have completed installing CPUs, memory, 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 vendor clusterware. Review your vendor documentation to complete these tasks, and if relevant, work with your vendor to complete such Oracle preinstallation steps that are listed here to confirm that the vendor hardware and software is correctly configured.

Server and network preparation for installation include the following:

1.2.1 Review Server Hardware and Software Requirements

The following is a summary of server hardware and software configuration.

Oracle Requires

Each node in a cluster requires the following:

  • Supported server hardware, including processors and system configuration.

    Review OracleMetaLink before starting installation on existing hardware, and before purchasing new hardware, to ensure that the hardware is supported with Oracle Clusterware with Oracle RAC 11g release 1 (11.1).

    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.
  • Operating system packages listed in system requirements.

    Customized operating system package installations are not supported, because they may not include required packages. You can add additional packages as needed, but if you subtract packages from the default packages set, then you may encounter "failed dependencies" errors for required software packages.

  • A supported interconnect software protocol on each node, to support Oracle Clusterware voting disk polling, and to support Cache Fusion with Oracle RAC. Your interconnect must be certified by Oracle for your platform.

Oracle Recommends: System Administrator Tasks

Oracle recommends the following to simplify server installation and maintenance, and prevent service issues

  • Enabling the Network Time Protocol feature of most operating systems, and ensuring that all nodes use the same reference Network Time Protocol server.

  • Configuring redundant switches, for all cluster sizes.

  • Using identical server hardware on each node, to simplify server maintenance.

Additional Options: System Administrators and Vendors

  • Though you do not need to use vendor clusterware with Oracle Clusterware, Oracle supports the use of many vendor clusterware options. However, you must install Oracle Clusterware to use Oracle RAC. Be aware that when you use vendor clusterware, Oracle Clusterware defers to the vendor clusterware for some tasks, such as node membership decisions.

  • You may require third-party vendor clusterware if you use a non-ethernet interconnect.

After you have set up server hardware, review "Checking Hardware Requirements" in the preinstallation chapter to ensure that your system has enough RAM, that the TMP and TEMP_DIR locations have enough available space for the installation, and that your system meets other hardware requirements.

1.2.2 Server Environment Configuration Overview

Configuring the server environment includes at least the following

  • Creating standard configuration operating system groups and users, as described in the preinstallation chapter. This includes creating specific operating system users to install and own Oracle software, and various other groups and users to enhance the security of your Oracle Clusterware, application, and data files.

  • Configuring the Oracle software owner user environments, as described in the Oracle Clusterware preinstallation chapters.

1.2.3 Oracle Base Overview

With Oracle Database 11g, during installation, you are prompted for the Oracle base path, instead of the Oracle home path.

In preparation for installation, Oracle recommends that you only set the ORACLE_BASE environment variable. 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.

For example, with Oracle Database 11g, Oracle recommends that you do not set an Oracle home environment variable, and instead allow OUI to create it. If the Oracle base path is /u01/app/oracle, then by default, OUI creates the following Oracle home path:

/u01/app/oracle/product/11.1.0/db_1

Note:

If you are upgrading from 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 1 (11.1). Similarly, if you have local Oracle homes on cluster nodes, then you must upgrade to local Oracle homes on cluster nodes.

1.2.4 Network Connections Overview

The following table provides an overview of network configuration requirements. Network administrators and system administrators can refer to the Preinstallation chapter in Oracle Clusterware Installation Guide for detailed configuration information.

Table 1-1 and the content following provides an overview of IP address requirements for network connections:

Table 1-1 Overview of IP Address Requirements for Each Node with Oracle Clusterware

IP Address Type Purpose Where Registered Pingable from Clients

Virtual IP address

Address for client requests and to be used to fail over requests to other nodes

DNS (recommended), or in the /etc/hosts file for each node in the cluster, and the /etc/hosts file for each node that is accessing the cluster database/

No, before installation; yes, after installation

Public IP address

Address for service requests

DNS, or in the /etc/hosts file for each node in the cluster.

Yes

Private IP address

Address for inter-node communication only

DNS, or /etc/hosts file for each node in the cluster. Must be resolvable only by other nodes in the cluster, and should be on dedicated network hardware.

No


The following is additional information about each address type

  • Virtual IP address: a public internet protocol (IP) address for each node, to be used as the Virtual IP address (VIP) for client connections. If a node fails, then Oracle Clusterware fails over the VIP address to an available node. This address should be in the /etc/hosts file on any client system that requires access to the database.

    During installation, the public VIP for each node is associated with the same interface name on every node that is part of your cluster. If you have a domain name server (DNS), then register the host names for the VIP with the DNS, so that it is resolvable from any client, as well as the cluster nodes. The VIP should not be in use at the time of the installation, because this is an IP address that Oracle Clusterware manages.

  • Public IP address: a public host name address for each node, typically assigned by the system administrator during initial system configuration. The public IP address name must be resolvable to the hostname. Register both the public IP and the VIP address with the DNS. If you do not have a DNS, then you must make sure that both public IP addresses are in the node /etc/hosts file (for all cluster nodes),

  • Private IP address: a private IP address for each node to serve as the private interconnect address for internode cluster communication only. The following must be true for each private IP address:

    • It must be separate from the public network

    • It must be accessible on the same network interface on each node

    • It must be connected to a network switch between the nodes for the private network; crosscable interconnects are not supported

    The private interconnect is used for internode communication by both Oracle Clusterware and Oracle RAC. The private IP address must be available in each node's /etc/hosts file. Oracle recommends that it is configured on a dedicated switch (or switches) that are not connected to anything other than the nodes in the same cluster.

    Note:

    All host names must conform to the RFC 952 standard, which permits alphanumeric characters. Host names using underscores ("_") are not allowed.

1.2.5 Secure Shell (SSH) Configuration Overview

Secure Shell (SSH) configuration is required for Oracle Clusterware and Oracle RAC.

System administrators can follow the procedure described in "Configuring SSH on All Cluster Nodes" in the Preinstallation chapter of Oracle Clusterware Installation Guide for your operating system, to configure SSH access for each node on the cluster to all other nodes of the cluster.

1.2.6 Browser Requirement Overview

You need a web browser to access documentation, and to use Oracle Enterprise Manager and 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 1.0.4

  • Firefox 1.5

  • Firefox 2.0

1.2.7 Platform-Specific Server Configuration Overview

Oracle Clusterware and Oracle RAC are tested with specific operating system kernels, and specific operating system components. Oracle requires that you use the operating system kernel and components that are certified for this release.

Oracle recommends that you or your system administrator review the system requirements carefully in Oracle Clusterware Installation Guide before beginning installation, to ensure that your system meets these requirements. If your system does not meet minimum operating system kernel 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 chapter, and check the OracleMetalink Certify page to ensure that you are aware of any additional requirements or recommendations for your specific hardware platform configuration.

1.3 Oracle RAC Storage Overview

To install Oracle RAC, you need to have configured external shared disks for storing the database files.

Refer to the "Configuring Oracle Real Application Clusters Storage" chapter in Oracle Clusterware Installation Guide for your operating system to review storage options for installation planning. Storage and system administrators can refer to this chapter to configure storage for Oracle Database files on Oracle RAC. Note that when Database Configuration Assistant (DBCA) configures automatic disk backup, it uses a database recovery area that must be shared.

See Also :

The Certify page on OracleMetalink for the most current information about storage options:
https://metalink.oracle.com

Oracle Database Storage Administrator's Guide for an overview of storage configuration administration

1.3.1 Overview of Oracle Database and Recovery File Options

There are three ways of storing Oracle Database and recovery files:

  • Automatic Storage Management: Automatic Storage Management (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.

    Note:

    For Standard Edition Oracle Database installations using Oracle RAC, ASM is the only supported storage option.
  • A supported shared file system: Supported file systems include the following:

    • A supported cluster file system: Note that if you intend to use a cluster file system for your data files, then you should create partitions large enough for the database files when you create partitions for Oracle Clusterware.

      See Also:

      The Certify page on OracleMetalink for supported cluster file systems
    • NAS Network File System (NFS) listed on Oracle Certify: Note that if you intend to use NFS for your data files, then you should create partitions large enough for the database files when you create partitions for Oracle Clusterware.

    See Also:

    The Certify page on OracleMetalink for supported Network Attached Storage (NAS) devices, and supported cluster file systems

    Note:

    Oracle Clusterware software can be installed on OCFS2. However, Oracle Clusterware software cannot be installed on Oracle Cluster File System (OCFS). Oracle Clusterware software can be installed on network-attached storage (NAS).

    For OCFS2 certification status, refer to the Certify page on OracleMetaLink:

  • Block or Raw Devices: A partition is required for each database file. If you do not use ASM, then for new installations on raw devices, you must use a custom installation.

    Note:

    On Linux, Oracle recommends using block devices for new installations.

1.3.2 General Storage Considerations for Oracle RAC

For all installations, you must choose the storage option that you want to use for Oracle Database files, or for Oracle Clusterware with Oracle RAC (Oracle RAC). If you want to enable automated backups during the installation, then you must also choose the 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.

For single-instance Oracle Database installations using Oracle Clusterware for failover, you must use OCFS2, ASM, block devices (on Linux), or shared raw disks if you do not want the failover processing to include dismounting and remounting of local file systems.

The following table 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.

Note:

For the most up-to-date information about supported storage options for Oracle RAC installations, refer to the Certify pages on the OracleMetaLink Web site:
https://metalink.oracle.com

Table 1-2 Supported Storage Options for Oracle Database and Recovery Files

Storage Option File Types Supported
Database Recovery

Automatic Storage Management

Yes

Yes

OCFS2

Yes

Yes

Red Hat Global File System (GFS); for Red Hat Enterprise Linux and Oracle Enterprise Linux

Yes

Yes

Local storage

No

No

NFS file system

Note: Requires a certified NAS device

Yes

Yes

Shared raw devices

Yes

No

Shared block devices

Yes

No


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 storage options for each file type provided that you satisfy all requirements listed for the chosen storage options.

  • Oracle recommends that you choose Automatic Storage Management (ASM) as the storage option for database and recovery files.

  • For Standard Edition Oracle RAC installations, ASM is the only supported storage option for database or recovery files.

  • You cannot use ASM to store Oracle Clusterware files, because these files must be accessible before any ASM instance starts.

  • If you intend to use ASM with Oracle RAC, and you are configuring a new ASM instance, then your system must meet the following conditions:

    • All nodes on the cluster have the 11g release 1 (11.1) version of Oracle Clusterware installed.

    • Any existing ASM instance on any node in the cluster is shut down.

  • If you intend to upgrade an existing Oracle RAC database, or an Oracle RAC database with ASM instances, 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 or Oracle RAC database with ASM instance is located.

    • The Oracle RAC database or Oracle RAC database with an ASM 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 database
  • 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.

1.4 Additional Information to Prepare for Installation

This section contains additional information about Oracle Clusterware, Oracle Automatic Storage Management, and Oracle RAC, that may be helpful for your installation plan team to read to decide how you want to configure your installation. It contains the following sections:

1.4.1 Oracle Clusterware and Vendor Clusterware

Oracle Clusterware provides clustering services. You do not require vendor clusterware when you use Oracle Clusterware. If you intend to install Oracle RAC, then you must install Oracle Clusterware.

1.4.2 Shared Components of Oracle RAC Installations

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 cluster file system or on shared disks, 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.

1.4.3 Oracle Database 11g Real Application Clusters Release Compatibility

You can install and operate different releases of Oracle Database software on the same computer:

  • When you have Oracle Clusterware installed with different release versions of Oracle software, the Oracle Clusterware version must be greater than or equal to the Oracle Database or Automatic Storage Management software version.

  • If you have an existing Oracle home, then you can create a new Oracle home and install Oracle Database 11g into the new Oracle home. You should install Oracle Clusterware in a separate Oracle Clusterware home. Note that if you intend to install Oracle Database 11g with RAC, then you must install Oracle Clusterware 11g. Each node can have only one Oracle Clusterware home. You can install Oracle RAC into a new home, and use OUI to deinstall and reinstall it as part of a test plan.

  • If you are running the Oracle9i release of Oracle RAC, 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 or a third party cluster software. Oracle Clusterware release 11g can be installed on the same system as Oracle9i database software, but Oracle9i software cannot be supported by Oracle Clusterware 11g.

    Note:

    If you want to remove third party cluster software after upgrading your database to Oracle Database 10g or Oracle Database 11g, then you must first remove the third party cluster software, and then re-install Oracle Clusterware.
  • If OUI detects a previous database release, then OUI asks you about your upgrade preferences. You have the option to upgrade one of the previous release databases with DBUA or to create a new database using DBCA. The information collected during this dialog is passed to DBUA or DBCA after the software is installed.

    If OUI detects a previous Oracle Clusterware release, then you are asked to upgrade the existing Oracle Clusterware installation. Only one Oracle Clusterware version can exist on a server, and servers must be members of one cluster only.

    Note:

    Do not move Oracle binaries from the Oracle home to another location. Doing so can cause dynamic link failures.
  • You can run different releases of Oracle Database and Automatic Storage Management (ASM). If the Oracle Database release and the ASM release are the same release, then they can both run out of the same Oracle home. If they are different releases, then the Oracle Database release and the ASM release must be in their separate release homes. For example, you can install an ASM release 11g release 1 (11.1) instance and use it with Oracle Database 10g release 2 (10.2) database, or you can install an Oracle 11g release 1 (11.1) database and use it with an ASM 10g release 2 (10.2) instance.

    Note:

    When using different release 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 ASM 11.1.0.2 instance will not be able to use new features available for ASM in the 11.1.0.2 release, but instead only ASM 10.2 features. Conversely, an Oracle Database 11g release 11.1.0.2 installation using an ASM instance release 10.2 will function like a release 10.2 database.

1.5 Confirming Cluster Readiness for Oracle RAC Installation with CVU

Before you start your installation, use Cluster Verification Utility (CVU) to ensure that your system is prepared for Oracle RAC installation. If any checks fail, then fix the errors reported, or contact your system or storage administrator to have the cause of the errors addressed.

CVU is available in the Oracle Clusterware home, in the bin directory. For example, if the Oracle Clusterware home is /crs, then the path is /crs/bin. To start CVU, navigate to the Clusterware home bin directory, and use the following command syntax:

cluvfy stage -pre dbinst -n nodelist -r release -osdba OSDBA -verbose

For example, with a two node cluster with nodeA and nodeB, where you are testing the cluster to prepare to install Oracle Database 11g with Oracle RAC, and your osdba group is dba, the following command checks for system readiness:

$ ./cluvfy stage -pre dbinst -n nodea,nodeb -r 11gR1 -osdba dba -verbose

For more information about CVU commands, enter ./cluvfy -help.

See Also:

Oracle Clusterware Administration and Deployment Guide for detailed information about CVU

1.6 Stopping Existing Oracle Processes for Upgrades or Coexisting Databases

If 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 upgrades

Table 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 11g release 1 (11.1)

No additional tasks. Refer to Installing Oracle Database 11g on a System with Oracle Database 10g

installing Oracle Database 11g release 1 (11.1) 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 1 (11.1)

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 1 (11.1) 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


Installing Oracle Database 11g on a System with Oracle Database 10g

If your system has an Oracle Database 10g installation, and you install Oracle Database 11g release 1 (11.1) 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.

Installing Oracle 11g Database on a System with Oracle9i Database Release 2

Explanation of Tasks If you are installing an Oracle Database 11g release 1 (11.1) 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 1 (11.1) 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 9.2 SRVM shared data is upgraded into an Oracle Cluster Registry that the 9.2 GSD will not be able to use. The 10.2 Oracle Clusterware installation starts an 11g release 1 (11.1) GSD to serve the Oracle9i 9.2 clients. To do this, refer to "Shutting down the Global Services Daemon"

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:

  1. Switch user to oracle:

    # su - oracle
    
  2. Enter the following command to determine if an Oracle Database 9i listener process is running and to identify its name and the Oracle home directory in which it is installed:

    $ ps -ef | grep tnslsnr
    

    This command displays information about the Oracle Net listeners running on the system:

    ... oracle_home1/bin/tnslsnr LISTENER -inherit
    

    In this example, oracle_home1 is the Oracle home directory where the listener is installed and LISTENER is the listener name.

  3. Set the ORACLE_HOME environment variable to specify the appropriate Oracle home directory for the listener:

    • Bourne, Bash, or Korn shell:

      $ ORACLE_HOME=oracle_home1
      $ export ORACLE_HOME
      
    • C or tcsh shell:

      % setenv ORACLE_HOME oracle_home1
      
  4. Enter the following command to identify the TCP/IP port number and IPC key value that the listener is using:

    $ $ORACLE_HOME/bin/lsnrctl status listenername
    

    Note:

    If the listener uses the default name LISTENER, then you do not have to specify the listener name in this command.
  5. Enter a command similar to the following to stop the listener process:

    $ $ORACLE_HOME/bin/lsnrctl stop listenername
    
  6. Repeat this procedure to stop all listeners running on this system and on all other nodes in the cluster.

Shutting down the Global Services Daemon As the oracle user, on each node of the cluster, use the following syntax to shut down the GSD:

$ cd 92_Oracle_home
$ bin/gsdctl stop

In the preceding syntax example, the variable 92_Oracle_home is the Oracle Database 9i release 2 (9.2) home.