Link to home
Start Free TrialLog in
Avatar of crishna1
crishna1Flag for United States of America

asked on

Oracle 11g Clusterware

I am installing Oracle Clusterware for the first time and i ran into the following errors.
What kind of  privileges does the user need to install, as you can see from the error message it seems like a privilege issue, please advice! I am loggedin as a user with administrator privileges.
Oracle Database 11g CRS Release - Production Copyright 1996, 2007 Oracle. All rights reserved.
2008-03-07 14:33:07.522: [  OCRRAW][2044]propriogid:1: INVALID FORMAT
2008-03-07 14:33:07.537: [  OCRRAW][2044]propriogid:1: INVALID FORMAT
2008-03-07 14:33:07.537: [  OCRRAW][2044]proprioini: both disks are not OCR formatted
2008-03-07 14:33:07.537: [  OCRRAW][2044]proprinit: Could not open raw device
2008-03-07 14:33:07.537: [ default][2044]a_init:7!: Backend init unsuccessful : [26]
2008-03-07 14:33:07.537: [ OCRCONF][2044]ocrconfig starts...
2008-03-07 14:34:06.081: [ OCRCONF][2044]Insufficient permission to proceed; require privileged user
2008-03-07 14:34:06.081: [ OCRCONF][2044]Exiting [status=failed]...
Avatar of sonicefu
Flag of Pakistan image

I think the user you are using to install is not a member of dba group  or ORA_DBA group.
During installation, you are asked to provide paths for two files that must be shared across all nodes of the cluster, either on a shared raw device, or a shared file system file:

The voting disk is a partition that Oracle Clusterware uses to verify cluster node membership and status.

The voting disk must be owned by the oracle user, must be in the dba group, and must have permissions set to 644. Provide at least 20 MB disk space for the voting disk.

The Oracle Cluster Registry (OCR) contains cluster and database configuration information for the RAC database and for Oracle Clusterware, including the node list, and other information about cluster configuration and profiles.

The OCR disk must be owned by root, must be in the oinstall group, and must have permissions set to 640. Provide at least 100 MB disk space for the OCR.

If your disks do not have external storage redundancy, then Oracle recommends that you provide one additional location for the OCR disk, and two additional locations for the voting disk. Creating redundant storage locations protects the OCR and voting disk in the event of a disk failure on the partitions you choose for the OCR and the voting disk.

Configuring Disk Devices for Oracle Clusterware Files
On Linux systems, O_DIRECT enables direct read and writes to block devices, avoiding kernel overhead. With Oracle Clusterware release 10.2 and later, Oracle Clusterware files are configured by default to use direct input/output.

With the 2. 6 kernel or later for Red Hat Enterprise Linux, Oracle Enterprise Linux, and SUSE Enterprise Server, you must create a permissions file to maintain permissions on Oracle Cluster Registry (OCR) and voting disk partitions. If you do not create this permissions file, then permissions on disk devices revert to their default values, root:disk, and Oracle Clusterware will fail to start.

On Asianux 2, Red Hat Enterprise Linux 4, and Oracle Enterprise Linux 4, you must create a permissions file number that is lower than 50.

On Asianux 3, Red Hat Enterprise Linux 5, Oracle Enterprise Linux 5, or SUSE Enterprise Linux 10, you must create a permissions file number that is higher at 50.

To configure a permissions file for disk devices, complete the following tasks:

Create a permissions file in /etc/udev/permissions.d, to change the permissions from default root ownership to root and members of the oinstall group, called 49-oracle.permissions, or 51-oracle.permissions, depending on your Linux distribution. In each case, the contents of the xx-oracle.permissions file are as follows:


For example, to set permissions for an OCR partition on block device /dev/sda1, create the following entry:

Use the section "Example of Creating a Udev Permissions File for Oracle Clusterware" for a step-by-step example of how to perform this task.

Configure the block devices from the local node with the required partition space for Oracle Clusterware files. Use the section "Example of Configuring Block Device Storage for Oracle Clusterware" to help you configure block devices, if you are unfamiliar with creating partitions.

Load updated block device partition tables on all member nodes of the cluster, using /sbin/partprobe devicename. You must do this as root.

Change the ownership of OCR partitions to the installation owner on all member nodes of the cluster. In the session where you run the Installer, the OCR partitions must be owned by the installation owner (crs, oracle) that performs the Oracle Clusterware installation. The installation owner must own the OCR partitions so that the Installer can write to them. During installation, the Installer changes ownership of the OCR partitions back to root. With subsequent system restarts, ownership is set correctly by the oracle.permissions file.

Enter the command /sbin/udevstart. This command should assign the permissions set in the oracle.permissions file. Check to ensure that your system is configured correctly.

4.4.1 Example of Creating a Udev Permissions File for Oracle Clusterware
The procedure to create a permissions file to grant oinstall group members write privileges to block devices is as follows:

Log in as root.

Change to the /etc/udev/permissions.d directory:

# cd /etc/udev/permissions.d
Start a text editor, such as vi, and enter the partition information where you want to place the OCR and voting disk files, using the syntax device[partitions]:root:oinstall:0640. Note that Oracle recommends that you place the OCR and the voting disk files on separate physical disks. For example, to grant oinstall members access to SCSI disks to place OCR files on sda1 and sdb2, and to grant the Oracle Clusterware owner (in this example crs) permissions to place voting disks on sdb3, sdc1 and sda2, add the following information to the file:

# OCR disks
# Voting disks
Save the file:

On Asianux 2, Enterprise Linux 4, and Red Hat Enterprise Linux 4 systems, save the file as 49-oracle.permissions.

On Asianux 3, Enterprise Linux 5, Red Hat Enterprise Linux 5, and SUSE Enterprise Server 10 systems, save the file as 51-oracle.permissions.

Using the following command, assign the permissions in the udev file to the devices:

# /sbin/udevstart
4.4.2 Example of Configuring Block Device Storage for Oracle Clusterware
The procedure to create partitions for Oracle Clusterware files on block devices is as follows:

log in as root

Enter the fdisk command to format a specific storage disk (for example, /sbin/fdisk /dev/sdb)

Create a new partition, and make the partition 280 MB in size for both OCR and voting disk partitions.

Use the command syntax /sbin/partprobe diskpath on each node in the cluster to update the kernel partition table for the shared storage device on each node.

The following is an example of how to use fdisk to create one partition on a shared storage block disk device for an OCR file:

[crs@localnode /] $ su
[root@localnode /] # /sbin/fdisk /dev/sdb
The number of cylinders for this disk is set to 1024.
Command (m for help): n
Command action
  e   extended
  P   primary partition (1-4)
Partition number (1-4): 1
First cylinder (1-1024, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-1024, default 1)
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-1024, default 1024):+280m

Command (m for help):w

The partition table has been altered!
Calling ioctl () to re-read partition table.
Synching disks.
[root@localnode /]#
[crs@localnode /] $ ssh remotenode
Last login Wed Feb 21 20:23:01 from localnode
[crs@remotenode ~]$ su
[root@localnode /] # /sbin/partprobe /dev/sdb1
Avatar of crishna1
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial