1 Summary List: Installing Oracle Clusterware

1.8.1 Check Existing SSH Configuration on the System

To determine if SSH is running, enter the following command:

$ ps -ef |grep sshd

If SSH is running, then the response to this command is one or more process ID numbers. In the home directory of the software owner that you want to use for the installation (crs, oracle), use the command ls -al to ensure that the .ssh directory is owned and writable only by the user.

1.8.2 Configure SSH on Cluster Member Nodes

Complete the following tasks on each node. You must configure SSH separately for each Oracle software installation owner that you intend to use for installation.

• Create .ssh, and create either RSA or DSA keys on each node

• Add all keys to a common authorized_keys file

1.8.3 Enable SSH User Equivalency on Cluster Member Nodes

After you have copied the authorized_keys file that contains all keys to each node in the cluster, start SSH on the node, and load SSH keys into memory. Note that you must either use this terminal session for installation, or reload SSH keys into memory for the terminal session from which you run the installation.

1.9.1 Create Disk Partitions for ASM Files OCR Disks, and Voting Disks

Create partitions as needed. For OCR and voting disks, create 280MB partitions for new installations, or use existing partition sizes for upgrades.

The following outlines the procedure for creating ASM, OCR or voting disk partitions without HP Serviceguard:

To configure shared raw disk devices for Oracle Clusterware files, database files, or both:

1. If you intend to use raw disk devices for database file storage, then choose a name for the database that you want to create.

   The name that you choose must start with a letter and have no more than four characters, for example, orcl.

2. Identify or configure the required disk devices.

   The disk devices must be shared on all of the cluster nodes.

3. To ensure that the disks are available, enter the following command on every node:

   # /usr/sbin/ioscan -fun -C disk
   

   The output from this command is similar to the following:

   Class  I  H/W Path    Driver S/W State   H/W Type     Description
   ==========================================================================
   disk    0  0/0/1/0.6.0 sdisk  CLAIMED     DEVICE       HP   DVD-ROM 6x/32x
                          /dev/dsk/c0t6d0   /dev/rdsk/c0t6d0
   disk    1  0/0/1/1.2.0 sdisk  CLAIMED     DEVICE      SEAGATE ST39103LC
                          /dev/dsk/c1t2d0   /dev/rdsk/c1t2d0
   

   This command displays information about each disk attached to the system, including the block device name (/dev/dsk/cxtydz) and the character raw device name (/dev/rdsk/cxtydz).

4. If the ioscan command does not display device name information for a device that you want to use, then enter the following command to install the special device files for any new devices:

   # /usr/sbin/insf -e
   

5. For each disk that you want to use, enter the following command on any node to verify that it is not already part of an LVM volume group:

   # /sbin/pvdisplay /dev/dsk/cxtydz
   

   If this command displays volume group information, then the disk is already part of a volume group. The disks that you choose must not be part of an LVM volume group.

   Note:

   If you are using different volume management software, for example VERITAS Volume Manager, then refer to the appropriate documentation for information about verifying that a disk is not in use.

6. If the ioscan command shows different device names for the same device on any node, then:

   1. Change directory to the /dev/rdsk directory.

   2. Enter the following command to list the raw disk device names and their associated major and minor numbers:

      # ls -la
      

      The output from this command is similar to the following for each disk device:

      crw-r--r--   1 bin        sys        188 0x032000 Nov  4  2003 c3t2d0
      

      In this example, 188 is the device major number and 0x32000 is the device minor number.

   3. Enter the following command to create a new device file for the disk that you want to use, specifying the same major and minor number as the existing device file:

      Note:

      Oracle recommends that you use the alternative device file names shown in the previous table.

      # mknod ora_ocr_raw_256m c 188 0x032000
      

   4. Repeat these steps on each node, specifying the correct major and minor numbers for the new device files on each node.

7. Enter commands similar to the following on every node to change the owner, group, and permissions on the character raw device file for each disk device that you want to use:

   Note:

   If you are using a multi-pathing disk driver with Automatic Storage Management, then ensure that you set the permissions only on the correct logical device name for the disk.

   If you created an alternative device file for the device, then set the permissions on that device file.

   • OCR:

     # chown root:oinstall /dev/rdsk/cxtydz
     # chmod 640 /dev/rdsk/cxtydz
     

   • Oracle Clusterware voting disk or database files:

     # chown oracle:dba /dev/rdsk/cxtydz
     # chmod 660 /dev/rdsk/cxtydz
     

8. If you are using raw disk devices for database files, then follow these steps to create the Oracle Database Configuration Assistant raw device mapping file:

   Note:

   You must complete this procedure only if you are using raw devices for database files. The Oracle Database Configuration Assistant raw device mapping file enables Oracle Database Configuration Assistant to identify the appropriate raw disk device for each database file. You do not specify the raw devices for the Oracle Clusterware files in the Oracle Database Configuration Assistant raw device mapping file.

   1. Set the ORACLE_BASE environment variable to specify the Oracle base directory that you identified or created previously:

      • Bourne, Bash, or Korn shell:

        $ ORACLE_BASE=/u01/app/oracle ; export ORACLE_BASE
        

      • C shell:

        % setenv ORACLE_BASE /u01/app/oracle
        

   2. Create a database file subdirectory under the Oracle base directory and set the appropriate owner, group, and permissions on it:

      # mkdir -p $ORACLE_BASE/oradata/dbname
      # chown -R oracle:oinstall $ORACLE_BASE/oradata
      # chmod -R 775 $ORACLE_BASE/oradata
      

      In this example, dbname is the name of the database that you chose previously.

   3. Change directory to the $ORACLE_BASE/oradata/dbname directory.

   4. Using any text editor, create a text file similar to the following that identifies the disk device file name associated with each database file.

      Oracle recommends that you use a file name similar to dbname_raw.conf for this file.

      Note:

      The following example shows a sample mapping file for a two-instance RAC cluster. Some of the devices use alternative disk device file names. Ensure that the device file name that you specify identifies the same disk device on all nodes.

      system=/dev/rdsk/c2t1d1
      sysaux=/dev/rdsk/c2t1d2
      example=/dev/rdsk/c2t1d3
      users=/dev/rdsk/c2t1d4
      temp=/dev/rdsk/c2t1d5
      undotbs1=/dev/rdsk/c2t1d6
      undotbs2=/dev/rdsk/c2t1d7
      redo1_1=/dev/rdsk/c2t1d8
      redo1_2=/dev/rdsk/c2t1d9
      redo2_1=/dev/rdsk/c2t1d10
      redo2_2=/dev/rdsk/c2t1d11
      control1=/dev/rdsk/c2t1d12
      control2=/dev/rdsk/c2t1d13
      spfile=/dev/rdsk/dbname_spfile_raw_5m
      pwdfile=/dev/rdsk/dbname_pwdfile_raw_5m
      

      In this example, dbname is the name of the database.

      Use the following guidelines when creating or editing this file:

      • Each line in the file must have the following format:

        database_object_identifier=device_file_name
        

        The alternative device file names suggested in the previous table include the database object identifier that you must use in this mapping file. For example, in the following alternative disk device file name, redo1_1 is the database object identifier:

        rac_redo1_1_raw_120m
        

      • For a RAC database, the file must specify one automatic undo tablespace datafile (undotbsn) and two redo log files (redon_1, redon_2) for each instance.

      • Specify at least two control files (control1, control2).

      • To use manual instead of automatic undo management, specify a single RBS tablespace datafile (rbs) instead of the automatic undo management tablespace data files.

   5. Save the file and note the file name that you specified.

   6. When you are configuring the oracle user's environment later in this chapter, set the DBCA_RAW_CONFIG environment variable to specify the full path to this file.

9. When you are installing Oracle Clusterware, you must enter the paths to the appropriate device files when prompted for the path of the OCR and Oracle Clusterware voting disk, for example:

   /dev/rdsk/cxtydz
   

1.12.1 Mark ASM Disk Partitions

For OUI to recognize a disk partition as an ASM disk candidate, you must mark the disk by logging in as root and marking the disk partitions that you created for ASM using the following command syntax, where ASM_DISK_NAME is the name of the ASM disk group, and device_name is the name of the disk device that you want to assign to that disk group:

/etc/init.d/oracleasm create disk ASM_DISK_NAME device_name