Installation guide

Oracle Bug 4679769: Failed to format OCR disk using CLSFMT.

Oracle Note 414163.1: 10gR2 RAC Install issues on Oracle EL5 or Red Hat Enterprise Linux 5 or SLES10

(VIPCA Failures).

Before running root.sh, download and apply the patch for Bug 4679769. If the root.sh script execution caused

the failure, erase the content of the OCR disks:

# dd if=/dev/zero of=/dev/raw/raw1 bs=1M count=25

# dd if=/dev/zero of=/dev/raw/raw2 bs=1M count=25

Before re-running root.sh, review Metalink Note 414163.1 to address known VIPCA issues.

Upon completion of the Oracle 10g R2 Clusterware installation, verify that it is working with the raw devices

bound to multipath devices:

[oracle]$ ocrcheck

Status of Oracle Cluster Registry is as follows :

Version : 2

Total space (kbytes) : 262144

Used space (kbytes) : 1164

Available space (kbytes) : 260980

ID : 1749049955

Device/File Name : /dev/raw/raw1

Device/File integrity check succeeded

Device/File Name : /dev/raw/raw2

Device/File integrity check succeeded

Cluster registry integrity check succeeded

# crsctl query css votedisk

0. 0 /dev/raw/raw4

1. 0 /dev/raw/raw5

2. 0 /dev/raw/raw6

located 3 votedisk(s).

# crsctl check crs

CSS appears healthy

CRS appears healthy

EVM appears healthy

Configuring Storage for ASM

Using ASM without ASMLib driver

ASM simplifies storage management for Oracle RAC and standalone systems with a large number of disks.

ASM is a user space process that can use Linux block devices directly. In Red Hat Enterprise Linux 5, it is rec-

ommended to use ASM with partitioned block devices. ASM processes should have read-write access to the

ASM partitions. Usually the ASM partitions should belong to user “oracle” and group “dba” and have permis-

sions 660.

You can use the udev utility to configure ASM device owner, group and permissions. A sample /etc/udev/

rules.d/39-oracle-multipath.rules file is shown below.