Download Oracle Clusterware Installation Guide for Linux

Create Storage
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 Create Storage
The following outlines the procedure for creating OCR and voting disk partitions on
block devices, and creating ASM disks on block devices.
For information, review the following sections in Chapter 4:
"Configuring Storage for Oracle Clusterware Files on a Supported Shared File System"
"Configuring Disk Devices for Oracle Clusterware Files"
1.9.1 Create Disk Partitions for ASM Disks, 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.
Every server running one or more database instances that use
ASM for storage has an ASM instance. In an Oracle RAC environment,
there is one ASM instance for each node, and the ASM instances
communicate with each other on a peer-to-peer basis.
Note:
Only one ASM instance is permitted for each node regardless of the
number of database instances on the node.
If you are upgrading an existing installation, then shut down ASM
instances before starting installation, unless otherwise instructed in
the upgrade procedure for your platform.
The following outlines the procedure for setting permissions for an ASM, OCR or
voting disk partition:
1.
On each node, create a permissions file in /etc/udev/permissions.d, to
change the permissions from default root ownership. On Red Hat Enterprise
Linux 4, Oracle Linux4, and Asianux Server, this file should be called
49-oracle.permissions, so that the kernel loads it before
50-udev.permissions. On Asianux Server 3, Oracle Linux 5, Red Hat
Enterprise Linux 5, and SUSE Enterprise Server 10 systems, this file should be
called 51-oracle.permissions, so that the kernel loads it after
50-udev.permissions.)
For each OCR partition, the contents of the xx-oracle.permissions file are as
follows:
devicepartition:root:oinstall:0640
For each voting disk partition, the contents of the xx-oracle.permissions file are as
follows:
devicepartition:crs_user:oinstall:0640
For each ASM disk partition, the contents of the xx-oracle.permissions file are as
follows:
Summary List: Installing Oracle Clusterware 1-5