Preparing the Nodes and Disks

This section contains the procedures that you need to prepare the nodes and disks.

How to Prepare the Nodes
How to Configure the Oracle Database Access Using Solaris Volume Manager
How to Configure the Oracle Database Access Using Veritas Volume Manager
How to Configure the Oracle Database Access Using Oracle ASM
How to Configure an Oracle Grid Infrastructure for Clusters SCAN Listener

How to Prepare the Nodes

Use this procedure to prepare for the installation and configuration of Oracle Database software.

Caution - Perform all of the steps in this section on all the nodes. If you do not perform all of the steps on all of the nodes, the Oracle Database installation is incomplete. An incomplete Oracle Database installation causes HA for Oracle to fail during startup.

Note - Consult the Oracle Database documentation before you perform this procedure.

The following steps prepare your nodes and install the Oracle Database software.

Become superuser on all of the cluster members.
Configure the cluster file system for HA for Oracle.

Caution - Raw devices from Oracle Solaris Cluster device groups are not supported in non-global zones.

If raw devices contain the databases, configure the global devices for raw device access. See the Oracle Solaris Cluster Software Installation Guide for information about how to configure global devices.
If you use the Solaris Volume Manager software, configure the Oracle Database software to use UNIX file system (UFS) logging on mirrored metadevices or raw-mirrored metadevices. See the Solaris Volume Manager documentation for more information about how to configure raw-mirrored metadevices.
If you use the Oracle Solaris ZFS file system for Oracle Database files, configure a highly available local ZFS file system. For more information, see How to Set Up the HAStoragePlus Resource Type to Make a Local Solaris ZFS Highly Available in Oracle Solaris Cluster Data Services Planning and Administration Guide.
If you use the Sun QFS file system, configure the Sun QFS file system for using with Oracle Database software. For more information on configuring the Sun QFS file system, see Using the Sun QFS Shared File System in Oracle Solaris Cluster Data Service for Oracle Real Application Clusters Guide.
Prepare the $ORACLE_HOME directory on a local or multihost disk.
Note - If you install the Oracle Database binaries on a local disk, use a separate disk if possible. Installing the Oracle Database binaries on a separate disk prevents the binaries from overwrites during operating environment reinstallation. When you use Oracle ASM you should create two $ORACLE_HOME directories, one $ORACLE_HOME directory for Oracle Database and the additional $ORACLE_HOME directory for Oracle ASM.
On each node or zone, create an entry for the database administrator (DBA) group in the /etc/group file, and add potential users to the group.
You typically name the DBA group dba. Verify that the oracle users are members of the dba group, and add entries as necessary for other DBA users. Ensure that the group IDs are the same on all of the nodes or zones that run HA for Oracle, as the following example illustrates.
```
dba:*:520:root,oracle
```
If you use Oracle ASM, you should add an additional entry for the DBA group in the /etc/group file for Oracle ASM.
```
dba:*:520:root,oracle,oraasm
```
You can create group entries in a network name service (for example, NIS or NIS+). If you create group entries in this way, add your entries to the local /etc/inet/hosts file to eliminate dependency on the network name service.
On each node or zone, create an entry for the Oracle Database user ID (oracle).
You typically name the Oracle Database user ID oracle. The following command updates the /etc/passwd and /etc/shadow files with an entry for the Oracle Database user ID.
```
# useradd -u 120 -g dba -d /Oracle_home oracle
```
Ensure that the oracle user entry is the same on all the nodes or zones that run HA for Oracle.
If you use Oracle ASM, you should create an additional Oracle Database user ID for Oracle ASM.
```
# useradd -u 121 -g dba -d /asm-home oraasm
```
If you are using Oracle Database 10.2.0.3 or higher, you should perform the following steps on each Oracle Solaris zone.
Note - You must perform these steps while creating a zone. If you fail to perform these steps, it results in an error. To resolve the error, you should set the necessary privileges and then run ORACLE_HOME/bin/localconfig reset ORACLE_HOME.
```
# zoneadm -z zcname halt
# zonecfg -z zcname info limitpriv
# zonecfg -z zcname set limitpriv=default,proc_priocntl
# zonecfg -z zcname info limitpriv
# zoneadm -z zcname boot
```

If you are using a zone cluster, configure the limitpriv property by using the clzonecluster command.

# clzonecluster configure zcname
clzonecluster:zcname>set limitpriv="default,proc_priocntl,proc_clock_highres"
clzonecluster:zcname>commit

On each zone-cluster node, prevent Oracle Clusterware time synchronization from running in active mode.
1. Log in to the zone-cluster node as root.
2. Create an empty /etc/inet/ntp.conf file.
```
# touch /etc/inet/ntp.conf
```

How to Configure the Oracle Database Access Using Solaris Volume Manager

Use this procedure to configure the Oracle database using Solaris Volume Manager.

Note - You can run this procedure only in the global zone.

Configure the disk devices for the Solaris Volume Manager software to use.
See Oracle Solaris Cluster Software Installation Guide for information about how to configure the Solaris Volume Manager software.
If you use raw devices to contain the databases, run the following commands to change each raw-mirrored metadevice's owner, group, and mode.
If you do not use raw devices, do not perform this step.
1. If you create raw devices, run the following commands for each device on each node that can master the Oracle Database resource group.
```
# chown oracle /dev/md/metaset/rdsk/dn
# chgrp dba /dev/md/metaset/rdsk/dn
# chmod 600 /dev/md/metaset/rdsk/dn
```
  metaset
  
  Specifies the name of the disk set
  
  /rdsk/dn
  
  Specifies the name of the raw disk device within the metaset disk set
2. Verify that the changes are effective.
```
# ls -lL /dev/md/metaset/rdsk/dn
```

How to Configure the Oracle Database Access Using Veritas Volume Manager

Use this procedure to configure the Oracle Database software using Veritas Volume Manager software.

Note - You can run this procedure only in the global zone.

Configure the disk devices for the VxVM software to use.
See the Oracle Solaris Cluster Software Installation Guide for information about how to configure Veritas Volume Manager.
If you use raw devices to contain the databases, run the following commands on the current disk-group primary to change each device's owner, group, and mode.
If you do not use raw devices, do not perform this step.
1. If you create raw devices, run the following command for each raw device.
```
# vxedit -g diskgroup set user=oracle group=dba mode=600 volume
```
  diskgroup
  
  Specifies the name of the disk group
  
  volume
  
  Specifies the name of the raw device within the disk group
2. Verify that the changes are effective.
```
# ls -lL /dev/vx/rdsk/diskgroup/volume
```
3. Synchronize the device group with the cluster to keep the VxVM namespace consistent throughout the cluster.
```
# cldevicegroup sync diskgroup
```

How to Configure the Oracle Database Access Using Oracle ASM

Use this procedure to configure the Oracle Database access using Oracle ASM. You can use Oracle ASM on VxVM or Solaris Volume Manager.

Configure the disk devices for the Oracle ASM software to use.
See the Using Oracle ASM in Oracle Solaris Cluster Data Service for Oracle Real Application Clusters Guide for information about how to configure Oracle ASM.
Set up the permissions for the Oracle ASM disks to be used by Oracle ASM disk groups.
1. Run the following commands for each device on each node that can master the Oracle Database resource group.
```
# chown oraasm:dba /dev/did/rdisk/dn
# chmod 660 /dev/did/rdisk/dn
```
2. Verify that the changes are effective.
```
# ls -lhL  /dev/did/rdisk/dn
```

How to Configure an Oracle Grid Infrastructure for Clusters SCAN Listener

When the HA for Oracle data service is deployed using Oracle Database 11g release 2 or 12c Grid Infrastructure for Clusters, the preferred listener for a single-instance database is an Oracle Grid Infrastructure for Clusters Single Client Access Name (SCAN) listener. To leverage a SCAN in the HA for Oracle configuration, you must modify the Oracle Database 11g release 2 or 12c single-instance database remote_listener parameter to reflect the SCAN name and port number.

If you configure a SCAN listener, you can ignore subsequent instructions in this manual about creating an Oracle Database listener resource with the SUNW.oracle_listener resource type. An Oracle Database listener resource is unnecessary when the SCAN listener is configured.

For more information about the SCAN, see Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Solaris Operating System.

The following example procedure shows the commands and sample output to configure the SCAN name and port. Perform this procedure on each node of the cluster.

Become superuser on the node.

Configure a SCAN listener.

# srvctl config scan
SCAN name: scanname, Network: 1/ipaddress/netmask/adaptername
SCAN VIP name: scanvip, IP: /ipalias/vipaddress

# srvctl config scan_listener
SCAN Listener LISTENER_SCAN1 exists. Port: TCP:portnumber
#

SQL> show parameters listener

NAME                TYPE     VALUE
------------------- -------- ------------------------------
listener_networks   string
local_listener      string   (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=nodename)
                             (PORT=portnumber))))
remote_listener     string


SQL>
SQL> alter system set remote_listener = 'scanname:portnumber' scope=both;

System altered.
SQL> show parameters listener

NAME                TYPE     VALUE
------------------- -------- ------------------------------
listener_networks   string
local_listener      string   (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=nodename)
                             (PORT=portnumber))))
remote_listener     string   scanname:portnumber
SQL>

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Data Service for Oracle Guide Oracle Solaris Cluster