test

Sun Cluster Data Service for Oracle RAC Guide for Solaris OS

Preparing the Sun Cluster Nodes

Preparing the Sun Cluster nodes modifies the configuration of the operating system to enable Oracle RAC to run on Sun Cluster nodes. Preparing the Sun Cluster nodes and disks involves the following tasks:

Caution – Caution –

Perform these tasks on all nodes where Sun Cluster Support for Oracle RAC can run. If you do not perform these tasks on all nodes, the Oracle installation is incomplete. An incomplete Oracle installation causes Sun Cluster Support for Oracle RAC to fail during startup.

Before You Begin

Before you prepare the Sun Cluster nodes, ensure that all preinstallation tasks for Oracle RAC are completed. For more information, see your Oracle RAC documentation.

ProcedureHow to Bypass the NIS Name Service

Bypassing the NIS name service protects the Sun Cluster Support for Oracle RAC data service against a failure of a cluster node's public network. A failure of a cluster node's public network might cause the NIS name service to become unavailable. If Sun Cluster Support for Oracle RAC refers to the NIS name service, unavailability of the name service might cause the Sun Cluster Support for Oracle RAC data service to fail.

Bypassing the NIS name service ensures that the Sun Cluster Support for Oracle RAC data service does not refer to the NIS name service when the data service sets the user identifier (ID). The Sun Cluster Support for Oracle RAC data service sets the user ID when the data service starts or stops the database.

  1. Become superuser on all nodes where Sun Cluster Support for Oracle RAC can run.

  2. On each node, include the following entries in the /etc/nsswitch.conf file.

    passwd:    files nis [TRYAGAIN=0]
publickey: files nis [TRYAGAIN=0]
project:   files nis [TRYAGAIN=0]
group:     files

    For more information about the /etc/nsswitch.conf file, see the nsswitch.conf(4) man page.

Next Steps

Go to How to Create the DBA Group and the DBA User Accounts.

ProcedureHow to Create the DBA Group and the DBA User Accounts

In installations of Oracle RAC with Sun Cluster, the DBA group is normally named dba. This group normally contains the root user and the oracle user.

Note –

This configuration of users and groups differs from the configuration that is described in the Oracle documentation for a standalone installation of Oracle RAC. A standalone installation of Oracle RAC uses a primary DBA group that is named oinstall and a secondary group that is named dba. Some applications also require a secondary group that is named oper. For more information, see your Oracle documentation.

Perform this task on each cluster node.

  1. On the node where you are performing this task, become superuser.

  2. Add an entry for the DBA group and potential users in the group to the /etc/group file.


    # echo 'group-name:*:group-id:user-list' >> /etc/group
    group-name

    Specifies the name of the group for which you are adding an entry. This group is normally named dba.

    group-id

    Specifies the group's unique numerical ID (GID) within the system.

    user-list

    Specifies a comma-separated list of the user names that are allowed in the group. Ensure that the list contains the names of all DBA users that are required. This group normally contains the root user and the oracle user.

    Ensure that the entry is identical on each node that can run Sun Cluster Support for Oracle RAC.

    You can create the name service entries in a network name service, such as the Network Information Service (NIS) or NIS+, so that the information is available to the data service clients. You can also create entries in the local /etc files to eliminate dependency on the network name service.

  3. Create the home directory of each potential user in the DBA group that you defined in Step 2.

    You are not required to create a home directory for the root user.

    For each potential user whose home directory you are creating, type the following command:


    # mkdir -p user-home
    user-home

    Specifies the full path of the home directory that you are creating.

  4. Add each potential user in the DBA group that you defined in Step 2 to the system.

    You are not required to add the root user.

    Use the useradd(1M) command to add each user. Adding a user to the system adds an entry for the user to the following files:

    • /etc/passwd

    • /etc/shadow 


    # useradd -u user-id -g group-name -d user-home[ -s user-shell] user-name
    -u user-id

    Specifies the user's unique numerical ID (UID) within the system.

    -g group-name

    Specifies the name of the user group of which the user is a member. You must specify the DBA group that you defined in Step 2.

    -d user-home

    Specifies the full path of the user's home directory. You must specify the home directory that you created for the user in Step 3.

    -s user-shell

    Optionally specifies the full path name of the program that is to be used as the user's shell when the user logs in. If you omit the -s option, the system uses the /bin/sh program by default. If you specify the -s option, user-shell must specify a valid executable file.

    user-name

    Specifies the user name of the user that you are adding. You must specify the name of a potential user in the DBA group that you defined in Step 2.

    Ensure that each user is identical on each node that can run Sun Cluster Support for Oracle RAC.

  5. Set the password of each user that you added in Step 4.

    Use the passwd(1) command to set the password of each user.

    1. Type the following command:


      # password user-name
      user-name

      Specifies the user name of the user whose password you are setting. You must specify the name of a user in the DBA group that you added in Step 4.

      The passwd command prompts you for the password.

    2. In response to the prompt, type the password and press Return.

      The passwd command prompts you to retype the password.

    3. In response to the prompt, retype the password and press Return.

  6. Change the ownership of each home directory that you created in Step 3 as follows:

    • Owner: the user for which you created the home directory

    • Group: the DBA group that you defined in Step 2

    For each home directory for which you are changing ownership, type the following command:


    # chown user-name:group-name user-home
    user-name

    Specifies the user name of the user for whose home directory you are changing ownership. You must specify the name of a user in the DBA group that you added in Step 4.

    group-name

    Specifies the name of the user group of which the user is a member. You must specify the DBA group that you defined in Step 2.

    user-home

    Specifies the full path of the user's home directory. You must specify the home directory that you created for the user in Step 3.

  7. Create a subdirectory of the /var/opt directory for each user in the DBA group that you added in Step 4.

    For each subdirectory that you are creating, type the following command:


    # mkdir /var/opt/user-name
    user-name

    Specifies the user name of the user whose subdirectory of the /var/opt directory you are creating. You must specify the name of a user in the DBA group that you added in Step 4.

  8. Change the ownership of each directory that you created in Step 7 as follows:

    • Owner: the user for which you created the directory

    • Group: the DBA group that you defined in Step 2

    For each directory for which you are changing ownership, type the following command:


    # chown user-name:group-name /var/opt/user-name
    user-name

    Specifies the user name of the user for whose home directory you are changing ownership. You must specify the name of a user in the DBA group that you added in Step 4.

    group-name

    Specifies the name of the user group of which the user is a member. You must specify the DBA group that you defined in Step 2.

Example 1–1 Creating the DBA Group and the DBA User Accounts

This example shows the sequence of commands for creating the DBA group dba, which is to contain the users root and oracle.

The dba group and the oracle user are created as follows:


# echo 'dba:*:520:root,oracle' >> /etc/group
# mkdir /Oracle-home
# useradd -u 120 -g dba -d /Oracle-home -s /bin/ksh oracle
# passwd oracle
New Password:oracle
Re-enter new Password:oracle
passwd: password successfully changed for oracle
# chown oracle:dba /Oracle-home
# mkdir /var/opt/oracle
# chown oracle:dba /var/opt/oracle
See Also

The following man pages:

Next Steps

Go to How to Configure Shared Memory for the Oracle RAC Software.

ProcedureHow to Configure Shared Memory for the Oracle RAC Software

Note –

Perform this task only if you are using the Solaris 10 OS. If you are using the Solaris 9 OS, perform the task for configuring kernel parameters in your Oracle RAC documentation.

To enable the Oracle RAC software to run correctly, you must ensure that sufficient shared memory is available on all the cluster nodes. Perform this task on each cluster node.

  1. Become superuser on a cluster node.

  2. Update the /etc/system file with the shared memory configuration information.

    You must configure these parameters on the basis of the resources that are available in the cluster. However, the value of each parameter must be sufficient to enable the Oracle RAC software to create a shared memory segment that conforms to its configuration requirements. For the minimum required value of each parameter, see your Oracle documentation.

    The following example shows entries to configure in the /etc/system file.


    *SHARED MEMORY/ORACLE
set shmsys:shminfo_shmmax=4294967295

  3. Shut down and reboot each node whose /etc/system file you updated in Step 2.

    Caution – Caution –

    Before you reboot, you must ensure that any volume manager software that is already installed is completely installed. An incomplete installation of volume manager software causes a panic. If you use VxVM, also ensure that you have installed the software and that the license for the VxVM cluster feature is valid. Otherwise, a panic occurs when you reboot. For information about how to recover from a node panic during installation, see Node Panic During Initialization of Sun Cluster Support for Oracle RAC.

    For detailed instructions, see Shutting Down and Booting a Single Cluster Node in Sun Cluster System Administration Guide for Solaris OS.

Next Steps

Go to Installing the Sun Cluster Support for Oracle RAC Packages.