Sun Cluster 3.0 U1 Data Services Installation and Configuration Guide

Previous: Chapter 7 Installing and Configuring Sun Cluster HA for Network File System (NFS)
Next: Chapter 9 Installing and Configuring Sun Cluster HA for SAP

Chapter 8 Installing and Configuring Sun Cluster HA for Oracle Parallel Server

This chapter describes the steps to install and configure the Sun Cluster HA for Oracle Parallel Server (OPS) data service on your Sun Cluster servers. This chapter contains the following procedures.

Overview

Use the procedures in the Oracle documentation to install and configure OPS. Although OPS is not registered with or managed by the Sun Cluster Resource Group Manager (RGM), OPS depends on the RGM to query cluster information.

You can configure OPS to use the shared-disk architecture of the Sun Cluster software. In this configuration, a single database is shared among multiple instances of OPS that access the database concurrently. The Oracle UNIX Distributed Lock Manager (UDLM) controls conflicting access to the same data. If a process or a node crashes, the UDLM is reconfigured to recover from the failure.

If a node failure occurs in an OPS environment, you can configure Oracle clients to reconnect to the surviving server without the use of the IP failover that Sun Cluster failover data services use. The Sun Cluster 3.0 U1 Concepts document describes this failover process.In an OPS environment, multiple Oracle instances cooperate to provide access to the same shared database. The Oracle clients can use any of the instances to access the database. Thus, if one or more instances have failed, clients can connect to a surviving instance and continue to access the database.

Installing and Configuring Sun Cluster HA for Oracle Parallel Server

The following table lists the sections that describe the installation and configuration tasks.

Table 8-1 Task Map: Installing and Configuring Sun Cluster HA for Oracle Parallel Server


Task	For Instructions, Go To ...
(Optional) Install volume management software	"Installing Volume Management Software With Sun Cluster HA for Oracle Parallel Server"
Install Sun Cluster HA for Oracle Parallel Server packages	"Installing Sun Cluster HA for Oracle Parallel Server Packages"
Install the UNIX Distributed Lock Manager and Oracle software	"Installing the Oracle Software"

Installing Volume Management Software With Sun Cluster HA for Oracle Parallel Server

For Sun Cluster HA for Oracle Parallel Server disks, you can use the following configurations.

VERITAS Volume Manager (VxVM) cluster utility
Sun StorEdge^TM A3500/A3500FC disk arrays with hardware RAID support

How to Use VxVM

To use the VxVM software with the Sun Cluster HA for Oracle Parallel Server data service, perform the following tasks.

Obtain a license for the Volume Manager cluster feature in addition to the basic VxVM license.

See your VxVM documentation for more information about VxVM licensing requirements.

Caution -
Failure to correctly install the license for the Volume Manager cluster feature might result in a panic when you install OPS support. Prior to installing the OPS packages, run the vxlicense check command to ensure that you have installed a valid license for the Volume Manager cluster feature.

Install and configure the VxVM software on the cluster nodes.

See the VxVM appendix in the Sun Cluster 3.0 U1 Installation Guide and the VxVM documentation for more information.

How to Use Sun StorEdge A3500/A3500FC Disk Arrays With Hardware RAID Support

If you use StorEdge A3500/A3500FC disk arrays with hardware RAID support and without VxVM software, configure raw device IDs (/dev/did/rdsk*) on top of the disk arrays' logical unit numbers (LUNs).

To set up the raw devices for OPS on a cluster that uses StorEdge A3500/A3500FC disk arrays with hardware RAID, perform the following steps.

Create LUNs on the disk arrays.

See the Sun Cluster 3.0 U1 Hardware Guide for information on how to create LUNs.

After you create the LUNs, run the format(1M) command to partition the disk arrays' LUNs into as many slices as you need.

The following example lists output from the format command.

# format

0. c0t2d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
   /sbus@3,0/SUNW,fas@3,8800000/sd@2,0
1. c0t3d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248>
   /sbus@3,0/SUNW,fas@3,8800000/sd@3,0
2. c1t5d0 <Symbios-StorEDGEA3000-0301 cyl 21541 alt 2 hd 64 sec 64>
   /pseudo/rdnexus@1/rdriver@5,0
3. c1t5d1 <Symbios-StorEDGEA3000-0301 cyl 21541 alt 2 hd 64 sec 64>
   /pseudo/rdnexus@1/rdriver@5,1
4. c2t5d0 <Symbios-StorEDGEA3000-0301 cyl 21541 alt 2 hd 64 sec 64>
   /pseudo/rdnexus@2/rdriver@5,0
5. c2t5d1 <Symbios-StorEDGEA3000-0301 cyl 21541 alt 2 hd 64 sec 64>
   /pseudo/rdnexus@2/rdriver@5,1
6. c3t4d2 <Symbios-StorEDGEA3000-0301 cyl 21541 alt 2 hd 64 sec 64>
   /pseudo/rdnexus@3/rdriver@4,2

Note -

If you use slice 0, do not start the partition at cylinder 0.

Run the scdidadm(1M) command to find the raw device ID (DID) that corresponds to the LUNs that you created in Step 1.

The following example lists output from the scdidadm -L command.

# scdidadm -L

1        phys-schost-1:/dev/rdsk/c0t2d0   /dev/did/rdsk/d1
1        phys-schost-2:/dev/rdsk/c0t2d0   /dev/did/rdsk/d1
2        phys-schost-1:/dev/rdsk/c0t3d0   /dev/did/rdsk/d2
2        phys-schost-2:/dev/rdsk/c0t3d0   /dev/did/rdsk/d2
3        phys-schost-2:/dev/rdsk/c4t4d0   /dev/did/rdsk/d3
3        phys-schost-1:/dev/rdsk/c1t5d0   /dev/did/rdsk/d3
4        phys-schost-2:/dev/rdsk/c3t5d0   /dev/did/rdsk/d4
4        phys-schost-1:/dev/rdsk/c2t5d0   /dev/did/rdsk/d4
5        phys-schost-2:/dev/rdsk/c4t4d1   /dev/did/rdsk/d5
5        phys-schost-1:/dev/rdsk/c1t5d1   /dev/did/rdsk/d5
6        phys-schost-2:/dev/rdsk/c3t5d1   /dev/did/rdsk/d6
6        phys-schost-1:/dev/rdsk/c2t5d1   /dev/did/rdsk/d6

Use the DID that the scdidadm output identifies to set up the raw devices.

For example, the scdidadm output might identify that the raw DID that corresponds to the disk arrays' LUNs is d4. In this instance, use the /dev/did/rdsk/d4sx raw device, where x is the slice number.

Installing Sun Cluster HA for Oracle Parallel Server Packages

Use this procedure to install the packages needed to run the Sun Cluster HA for Oracle Parallel Server data service.

How to Install Sun Cluster HA for Oracle Parallel Server Packages

To complete this procedure, you need the Sun Cluster Agents CD. Perform this procedure on all cluster nodes that can run Sun Cluster HA for Oracle Parallel Server.

Load the Agents CD into the CD-ROM drive.

Install the Sun Cluster HA for Oracle Parallel Server packages.

The packages vary, depending on whether you use hardware RAID or VERITAS Volume Manager for your volume manager.
1. If you use hardware RAID as your volume manager, install as follows.
  # pkgadd -d . SUNWscucm SUNWudlm SUNWudlmr SUNWschwr
2. If you use VERITAS Volume Manager as your volume manager, install as follows.
  # pkgadd -d . SUNWscucm SUNWudlm SUNWudlmr SUNWcvmr SUNWcvm

Caution -

After you have installed the Sun Cluster HA for Oracle Parallel Server packages, do not reboot the nodes until the Oracle UDLM package is installed, otherwise a panic occurs.

Where to Go From Here

Go to "Installing the Oracle Software" to install the UDLM and Oracle software.

Installing the Oracle Software

Use the procedures in this section to perform the following tasks.

Prepare the Sun Cluster nodes.
Install the Oracle UDLM software.
Install the Oracle RDBMS software.

How to Prepare the Sun Cluster Nodes

For the UDLM software to run correctly, sufficient shared memory must be available on all cluster nodes. See the OPS CD for all installation instructions. To prepare the Sun Cluster nodes, check that the following tasks have been completed.

The Oracle user account and the dba group are set up correctly.
The system is configured to support the shared memory requirements of the UDLM.

Note -

Perform the following steps as superuser on each cluster node.

On each node, create an entry for the database administrator group in the /etc/group file, and add potential users to the group.

This group normally is named dba. Verify that root and oracle are members of the dba group, and add entries as necessary for other DBA users. Verify that the group IDs are the same on all the nodes that run the Sun Cluster HA for Oracle Parallel Server data service. For example, add the following entry to the /etc/group file.
dba:*:520:root,oracle
You can make the name-service entries in a network name service (for example, NIS or NIS+) so that the information is available to Sun Cluster HA for Oracle Parallel Server clients. You can also make entries in the local /etc files to eliminate dependency on the network name service.

On each node, create an entry for the Oracle user ID (the group and password) in the /etc/passwd file, and run the pwconv(1M) command to create an entry in the /etc/shadow file.

This Oracle user ID is normally oracle. For example, add the following entry to the /etc/passwd file.
# useradd -u 120 -g dba -d /Oracle-home oracle
Ensure that the user IDs are the same on all the nodes that run the Sun Cluster HA for Oracle Parallel Server data service.

Where to Go From Here

After you set up the cluster environment for OPS, install the UDLM software on each cluster node. See your OPS installation documentation for instructions.

How to Install the UDLM Software

You must install the UDLM software on the local disk of each node.

Become superuser on a cluster member.

Install the UDLM software.

See the appropriate OPS installation documentation.

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

You must configure these parameters based on the resources available in the cluster. Decide on the appropriate values, but be sure that the UDLM can create a shared memory segment according to its configuration requirements. The following is an example of the entries to configure in /etc/system.

*SHARED MEMORY/ORACLE
set shmsys:shminfo_shmmax=268435456
set semsys:seminfo_semmap=1024
set semsys:seminfo_semmni=2048
set semsys:seminfo_semmns=2048
set semsys:seminfo_semmsl=2048
set semsys:seminfo_semmnu=2048
set semsys:seminfo_semume=200
set shmsys:shminfo_shmmin=200
set shmsys:shminfo_shmmni=200
set shmsys:shminfo_shmseg=200
forceload: sys/shmsys
forceload: sys/semsys
forceload: sys/msgsys

Shut down and reboot all the nodes.

Caution -
Before you reboot, ensure that the VxVM software is installed correctly and the license for cluster operation is valid. Also ensure that the UDLM software is installed and configured correctly. Otherwise, a panic occurs.

See the scshutdown(1M) man page for details.

First, run the following command on one node to shut down all of the nodes.
phys-schost-1# scshutdown -g0 -y
For each node, run the following command at the ok prompt.
ok boot

Where to Go From Here

After you have installed the UDLM software on each cluster node and rebooted all the nodes, install the Oracle RDBMS software. See the OPS installation documentation for instructions.

How to Install the Oracle RDBMS Software

See your OPS installation documentation for instructions on installing the RDBMS software.

Where to Go From Here

See the instructions in the Oracle documentation to create your Oracle database when you install the Oracle RDBMS software.