Oracle Database 11g Release 2 Real Application Clusters with SLVM/RAW on HP-UX Installation Cookbook, September 2010

• If you want to use Oracle on RAW devices and Async I/O is not configured, then

– Create the /dev/async character device

# /sbin/mknod /dev/async c 101 0x0

# chown oracle:dba /dev/async

# chmod 660 /dev/async

– Configure the async driver in the kernel using SAM or HP SMS.

– Set HP-UX kernel parameter max_async_ports using SAM. max_async_ports limits the

maximum number of processes that can concurrently use /dev/async. Set this parameter to the

sum of “processes” from init.ora + number of background processes. If max_async_ports is

reached, subsequent processes will use synchronous i/o.

– Set HP-UX kernel parameter aio_max_ops using SAM. aio_max_ops limits the maximum

number of asynchronous i/o operations that can be queued at any time. Set this parameter to the

default value (2048), and monitor over time using glance

• To allow you to successfully relink Oracle products after installing this software, please ensure that

the following symbolic links have been created:

# cd /usr/lib

# ln -s /usr/lib/libX11.3 libX11.sl

# ln -s /usr/lib/libXIE.2 libXIE.sl

# ln -s /usr/lib/libXext.3 libXext.sl

# ln -s /usr/lib/libXhp11.3 libXhp11.sl

# ln -s /usr/lib/libXi.3 libXi.sl

# ln -s /usr/lib/libXm.4 libXm.sl

# ln -s /usr/lib/libXp.2 libXp.sl

# ln -s /usr/lib/libXt.3 libXt.sl

# ln -s /usr/lib/libXtst.2 libXtst.sl

• Ensure that each member node of the cluster is set (as closely as possible) to the same date and

time. Oracle strongly recommends using the Network Time Protocol feature of most operating

systems for this purpose, with all nodes using the same reference Network Time Protocol server.

Note: Oracle Grid Infrastructure Installation Guide 11gR2 for HP-UX

should be referred for latest

hardware requirement.

Network Requirements

You need the following IP addresses per node to build a RAC 11g cluster:

• Public interface that will be used for client communication

• Virtual IP address (VIP) that will be bind by Oracle Clusterware to the public interface. It will be

used by clients to access the RAC database. If a node or interconnect fails, then the affected VIP is

relocated to the surviving node.

• Private interface that will be used for inter-cluster traffic. There are three major categories of

inter-cluster traffic:

– SG-HB = Serviceguard heartbeat and communications traffic. It is recommended to use two active

networks for SG HB.

– CSS-HB = Oracle CSS heartbeat traffic and communications traffic for Oracle Clusterware.

CSS-HB uses a single logical connection over a single subnet network.

– RAC-IC = RAC instance peer to peer traffic and communications for Global Cache Service (GCS) and

Global Enqueue Service (GES), formally Cache Fusion (CF) and Distributed Lock Manager (DLM).