Skip Headers
Oracle® Real Application Clusters Installation and Configuration Guide
10g Release 1 (10.1.0.3) for Linux x86-64
Part No. B14406-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

3 Installing Cluster Ready Services on Linux Systems

This chapter describes the procedures for installing Cluster Ready Services (CRS) on UNIX, phase one of the Oracle Database 10g Real Application Clusters installation on Linux systems. The topics in this chapter are:

Installation Setup Procedures

Perform the following procedures to complete phase one of the installation of the Oracle Database 10g with RAC.

  1. Verify user equivalence by executing the ssh command on the local node with the date command argument using the following syntax:

    ssh node_name date
    
    

    The output from this command should be the timestamp of the remote node identified by the value that you use for node_name. If ssh is in the /usr/local/bin directory, then use ssh to configure user equivalence.

    You cannot use ssh to verify user equivalence if ssh is in another location in your PATH. In this case, use rsh to confirm user equivalence.

  2. In addition to the host machine's public internet protocol (IP) address, obtain two more IP addresses for each node that is going to be part of your installation. During the installation, enter the IP addresses into DNS. One of the IP addresses must be a public IP address for the node's virtual IP address (VIP). Oracle uses VIPs for client-to-database connections. Therefore, the VIP address must be publicly accessible. The other address must be a private IP address for inter-node, or instance-to-instance Cache Fusion traffic. Using public interfaces for Cache Fusion can cause performance problems.

Installing Cluster Ready Services with the OUI

This section describes the procedures for using the Oracle Universal Installer (OUI) to install CRS. Note that the CRS home that you identify in this phase of the installation is only for CRS software; this home cannot be the same home as the home that you will use in phase two to install the Oracle Database 10g software with RAC.


Note:

For Linux, you cannot install the Oracle Database 10g Cluster Ready Services software on the Oracle Database 10g Linux cluster file system.

  1. If a GSD from Oracle9i, Release 9.2 or earlier, is running, then stop it before installing Oracle Database 10g CRS by executing the following command from the GSD's Oracle home:

    $ORACLE_HOME/bin/gsdctl stop
    
    

    If you are installing CRS on a node that already has a single-instance Oracle Database 10g installation, then perform the following operations:

    1. If there are any ASM instances running on the node, stop these existing ASM instances. After CRS is installed, restart the ASM instances again. This ensures that they are associated with the new cluster software.

    2. Log on as the root user and stop all Oracle services by executing the command:

      Oracle home/bin/localconfig delete
      
      

      where Oracle home is the home that is running CSS.

  2. Log in as the oracle user and set the ORACLE_BASE environment variable to specify the Oracle base directory that you created previously, for example /u01/app/oracle.

  3. Set the ORACLE_HOME environment variable to specify the CRS home directory that you created previously, for example /u01/crs/oracle/product/10.1.0/crs_1.

  4. Run the runInstaller command from the top-level directory of the Oracle Cluster Ready Services Release 1 CD-ROM or the crs directory on the DVD-ROM. These are separate CD-ROMs and DVD-ROMs that contain the Cluster Ready Services software. When the OUI displays the Welcome page, click Next.

  5. Depending on whether your environment has an Oracle inventory, the following scenarios apply:

    • If you are performing this installation in an environment where the OUI inventory is already set up, then the OUI displays the Specify File Locations page. If the Specify File Locations page appears, proceed to Step 7.

    • If you are performing this installation in an environment in which you have never installed Oracle database software, in other words the environment does not have an OUI inventory, then the OUI displays the Specify Inventory Directory and Credentials page. Enter the inventory location and the UNIX group name information into the Specify Inventory Directory and Credentials page, click Next, and the OUI displays a dialog.

  6. The OUI dialog indicates that you should run the oraInventory location/orainstRoot.sh script. Run the orainstRoot.sh script as root user, click Continue, and the OUI displays the Specify File Locations page.

  7. The Specify File Locations Page contains predetermined information for the source of the installation files and the target destination information. Enter the CRS home name and its location in the target destination, click Next, and the OUI displays the Language Selection page.


    Note:

    The CRS home that you identify in this step must be different from the Oracle home that you will use in phase two of the installation.

  8. In the Language Selection page select the languages that you want CRS to use, click Next, and the OUI displays the Cluster Configuration page.

  9. In the Specify Network Interface Usage page the OUI displays a list of cluster-wide interfaces. Use the drop-down menus on this page to classify each interface as Public, Private, or Do Not Use. The default setting for each interface is Do Not Use. You must classify at least one interconnect as Public and one as Private.

  10. When you click Next on the Specify Network Interface Usage page, the OUI will look for the ocr.loc file. The OUI will look in the directory. If the ocr.loc file exists, and if the ocr.loc file has a valid entry for the Oracle Cluster Registry (OCR) location, then the Voting Disk Location page appears and you should proceed to Step 11.

    Otherwise, the Oracle Cluster Registry Location Information page appears. Enter a complete path for the raw device or shared file system file for the Oracle Cluster Registry, click Next, and the Voting Disk Information page appears.

  11. On the Voting Disk Information page, enter a complete path and file name for the file in which you want to store the voting disk and click Next. This must be a shared raw device or a shared file system file.


    Notes:

    • The storage size for the OCR should be at least 100MB and the storage size for the voting disk should be at least 20MB. In addition, Oracle recommends that you use a RAID array for storing the OCR and the voting disk to ensure the continuous availability of the partitions.

    • The OCR disk must be owned by root, be in the dba group, and have permissions set to 640; the voting disk must be owned by oracle, be in the dba group, and have permissions set to 644.



    See Also:

    The pre-installation chapters in Part II for information about the minimum raw device sizes

  12. After you complete the Voting Disk Information page and click Next, if the Oracle inventories on the remote nodes are not set up, then the OUI displays a dialog asking you to run the orainstRoot.sh script on all of the nodes. After the orainstRoot.sh script processing completes, the OUI displays a Summary page.

  13. The OUI displays the list of components that will be installed on the Summary page. Review the list of components and click install.

    During the installation, unless you are using a clustered file system for the CRS home, the OUI first copies software to the local node and then copies the software to the remote nodes. Then the OUI displays a dialog indicating that you must run the root.sh script on all the nodes that are part of this installation.

  14. Before running the root.sh script, log in as root and change permissions on the parent directories of the CRS home directory to permit only the root user to write to those directories. For example, if the CRS home directory is /u01/crs/oracle/product/10.1.0/crs_1, then enter commands similar to the following:

    # chmod go-w /u01/crs/oracle/product/10.1.0
    # chmod go-w /u01/crs/oracle/product
    # chmod go-w /u01/crs/oracle/
    # chmod go-w /u01/crs/
    # chmod go-w /u01
    
    

    Note:

    You must perform this step on all of the nodes that are part of this installation session if you are not installing the CRS software on a cluster file system.

  15. In the same terminal window, run the root.sh script as the root user. Execute the root.sh script on one node at a time. Only start another session of root.sh on another node after the previous root.sh execution completes; do not execute root.sh on more than one node at a time.

    After you have run the root.sh script on all of the nodes that are part of this installation and when the final root.sh script has completed, return to the OUI and click OK on the dialog. The OUI runs the Oracle Notification Server Configuration Assistant and Oracle Private Interconnect Configuration Assistant. These assistants run without your intervention.

  16. When the OUI displays the End of Installation page, click Exit to exit the Installer.

  17. Unset the ORACLE_HOME environment variable.

  18. Verify your CRS installation by executing the following olsnodes command from the CRS Home/bin directory:

    olsnodes
    
    

    The output from this command should be a listing of the nodes on which CRS was installed, as shown in the following example:

    $ cd /opt/oracle/app/product/10.1.0/crs_1/bin$ ./olsnodes -n
    
    racserver1      1racserver2      2
    
    

At this point, you have completed phase one, the installation of Cluster Ready Services, and are ready to install the Oracle Database 10g with RAC as described in Chapter 4, "Installing Oracle Database 10g with Real Application Clusters".

Oracle assumes that when you install Oracle Database 10g Cluster Ready Services software, that you will also install the Oracle Database 10g with RAC software. If there will be a significant delay before you perform phase two of the RAC installation to install Oracle Database 10g with RAC software, then run CRS_Home/bin/gsdctl start to start the GSD manually to service the 9.2 SRVCTL tool and assistants. Then before installing the Oracle Database 10g with RAC software, run the command CRS_Home/bin/gsdctl stop to stop the GSD.

Cluster Ready Services Background Processes

The following processes must be running in your environment after the CRS installation in order for Cluster Ready Services to function:

  • evmd -- Event manager daemon that starts the racgevt process to manage callouts.

  • ocssd -- Manages cluster node membership and runs as oracle user; failure of this process results in cluster restart.

  • crsd -- Performs high availability recovery and management operations such as maintaining the OCR. Also manages application resources and runs as root user and restarts automatically upon failure.