Just making oracle as member of disk group on all nodes should work:
$grep oracle /etc/group
dba:!:104:oracle
disk:x:6:oracle
-Arun
>>> On 1/12/2007 at 2:46 PM, "Thomas Gorsitzke"
<thomas.gorsitzke@(protected)>
wrote:
> Note that the OCR (OCR + mirror) and the voting disk(s) for Oracle
> Clusterware 10.2 need to be on a shared raw device with special
permissions.
>
> chown root:oinstall /dev/raw/raw1 # ocr
> chown oracle:oinstall /dev/raw/raw2 # voting
> chmod 640 /dev/raw/raw1
> chmod 644 /dev/raw/raw2
>
> They must be raw devices - it's a Universal Installer feature.
>
>
> Regards,
> Thomas
>
> -------------------------------------------
> THOMAS GORSITZKE
>
> Senior Principal Consultant
> Consulting Expert Services Competence Group
> ORACLE Deutschland GmbH
>
>
>> -----Urspr??ngliche Nachricht-----
>> Von: Alexei_Roudnev [mailto:Alexei_Roudnev@(protected)]
>> Gesendet: Freitag, 12. Januar 2007 20:14
>> An: LOPEZ DIAZ, JORGE; suse-oracle@(protected)
>> Betreff: Re: [suse-oracle] ASM and Mutilpath
>>
>> Can you verify, that Oracle is a member of 'disk' group?
>>
>>
>> ----- Original Message -----
>> From: "LOPEZ DIAZ, JORGE" <jorge.lopez@(protected)>
>> To: <suse-oracle@(protected)>
>> Sent: Friday, January 12, 2007 4:13 AM
>> Subject: RE: [suse-oracle] ASM and Mutilpath
>>
>>
>>
>> Well, I configured multipath and udev like note 357472.1 recommends,
but
>> still I can't see dm devices or disk/by-name or mapper devices from
ASM
>> configuration screen.
>>
>> udev.permissions:
>>
>> dm-*:root:disk:0660
>> disk/by-name/asm*:root:disk:0660
>>
>> ls -l /dev/dm-*
>>
>> brw-rw---- 1 root disk 253, 0 Jan 11 19:14 /dev/dm-0
>> brw-rw---- 1 root disk 253, 1 Jan 11 19:14 /dev/dm-1
>> brw-rw---- 1 root disk 253, 10 Jan 11 19:14 /dev/dm-10
>> brw-rw---- 1 root disk 253, 11 Jan 11 19:14 /dev/dm-11
>> brw-rw---- 1 root disk 253, 12 Jan 11 19:14 /dev/dm-12
>> brw-rw---- 1 root disk 253, 13 Jan 11 19:14 /dev/dm-13
>> brw-rw---- 1 root disk 253, 14 Jan 11 19:14 /dev/dm-14
>> brw-rw---- 1 root disk 253, 2 Jan 11 19:14 /dev/dm-2
>> brw-rw---- 1 root disk 253, 3 Jan 11 19:14 /dev/dm-3
>> brw-rw---- 1 root disk 253, 4 Jan 11 19:14 /dev/dm-4
>> brw-rw---- 1 root disk 253, 5 Jan 11 19:14 /dev/dm-5
>> brw-rw---- 1 root disk 253, 6 Jan 11 19:14 /dev/dm-6
>> brw-rw---- 1 root disk 253, 7 Jan 11 19:14 /dev/dm-7
>> brw-rw---- 1 root disk 253, 8 Jan 11 19:14 /dev/dm-8
>> brw-rw---- 1 root disk 253, 9 Jan 11 19:14 /dev/dm-9
>>
>> ls -l /dev/disk/by-name
>>
>> lrwxrwxrwx 1 root disk 10 Jan 11 19:14 asmgoma1b -> ../../dm-2
>> lrwxrwxrwx 1 root disk 10 Jan 11 19:14 asmgoma2b -> ../../dm-1
>> lrwxrwxrwx 1 root disk 10 Jan 11 19:14 asmmama1a -> ../../dm-7
>> lrwxrwxrwx 1 root disk 10 Jan 11 19:14 asmmama1b -> ../../dm-8
>> lrwxrwxrwx 1 root disk 10 Jan 11 19:14 asmmama2a -> ../../dm-5
>> lrwxrwxrwx 1 root disk 10 Jan 11 19:14 asmmama2b -> ../../dm-6
>> lrwxrwxrwx 1 root disk 10 Jan 11 19:14 asmmama3a -> ../../dm-9
>> lrwxrwxrwx 1 root disk 11 Jan 11 19:14 asmmama3b -> ../../dm-10
>> lrwxrwxrwx 1 root disk 10 Jan 11 19:14 asmteam1b -> ../../dm-0
>> lrwxrwxrwx 1 root disk 11 Jan 11 19:14 asmteam2b -> ../../dm-14
>> lrwxrwxrwx 1 root disk 11 Jan 11 19:14 asmteam3b -> ../../dm-11
>> lrwxrwxrwx 1 root disk 11 Jan 11 19:14 dm-12 -> ../../dm-12
>> lrwxrwxrwx 1 root disk 11 Jan 11 19:14 dm-13 -> ../../dm-13
>> lrwxrwxrwx 1 root disk 10 Jan 11 19:14 dm-3 -> ../../dm-3
>> lrwxrwxrwx 1 root disk 10 Jan 11 19:14 flashrec -> ../../dm-4
>>
>> ls -l /dev/mapper
>>
>> brw-rw---- 1 root disk 253, 2 Jan 11 19:14 asmgoma1b
>> brw-rw---- 1 root disk 253, 1 Jan 11 19:14 asmgoma2b
>> brw-rw---- 1 root disk 253, 7 Jan 11 19:14 asmmama1a
>> brw-rw---- 1 root disk 253, 8 Jan 11 19:14 asmmama1b
>> brw-rw---- 1 root disk 253, 5 Jan 11 19:14 asmmama2a
>> brw-rw---- 1 root disk 253, 6 Jan 11 19:14 asmmama2b
>> brw-rw---- 1 root disk 253, 9 Jan 11 19:14 asmmama3a
>> brw-rw---- 1 root disk 253, 10 Jan 11 19:14 asmmama3b
>> brw-rw---- 1 root disk 253, 0 Jan 11 19:14 asmteam1b
>> brw-rw---- 1 root disk 253, 14 Jan 11 19:14 asmteam2b
>> brw-rw---- 1 root disk 253, 11 Jan 11 19:14 asmteam3b
>> lrwxrwxrwx 1 root disk 16 Jan 11 19:14 control ->
../device-mapper
>> brw-rw---- 1 root disk 253, 12 Jan 11 19:14 dm-12
>> brw-rw---- 1 root disk 253, 13 Jan 11 19:14 dm-13
>> brw-rw---- 1 root disk 253, 3 Jan 11 19:14 dm-3
>> brw-rw---- 1 root disk 253, 4 Jan 11 19:14 flashrec
>>
>> (asmxxxxxx are devices for ASM)
>>
>>
>> Group and permissions set by hand because udev.permissions (I had
to create
>> it) seems not to function properly.
>>
>> Is there anything wrong or missing?
>>
>>
>>
>> ________________________________
>>
>>
>>
>> Jorge L??pez D??az
>> T??cnico de Gesti??n Inform??tica
>> Consejer??a de Sanidad
>>
>>
>> -----Mensaje original-----
>> De: LOPEZ DIAZ, JORGE
>> Enviado el: jueves, 11 de enero de 2007 18:54
>> Para: suse-oracle@(protected)
>> Asunto: RE: [suse-oracle] ASM and Mutilpath
>>
>> Hello Michael,
>>
>>
>>
>> I've been reading note Metalink Note 357472.1 (thanks Clemens), so I
wil
>> configure udev, multipath, etc. according it. The idea is not to use
raw
>> devices, except for voting disk and OCR. If this is not possible at
all, I
>> will configure raw devices like you made it.
>>
>>
>>
>> I'll let know you, and every body, how this results.
>>
>>
>>
>>
>>
>>
>>
>> De: Michael Kershaw [mailto:mike.kershaw@(protected)]
>> Enviado el: jueves, 11 de enero de 2007 18:09
>> Para: LOPEZ DIAZ, JORGE
>> Asunto: Re: [suse-oracle] ASM and Mutilpath
>>
>>
>>
>> Hey Jorge,
>>
>> We've built two (18) node Sles9 clusters running 10g w/ ASM
using
>> Hitachi Lightning fiber disk utilizing the multipath-tools package,
and
>> everything is running pretty smoothely minus that of the buggy ASM
that is
>> being worked on closely with Oracle. The way we have it configured,
is the
>> fiber disks are presented down two separate fiber channels, I take
the UID
>> of the luns, put them in a /etc/multipath.conf file, alias them to
whichever
>> device they will be used for(ie. raw104), and when the devices get
aliased,
>> the aliases reside in /dev/mapper/. From there, I've created the
/etc/raw
>> file, and bind the raw device names to the /dev/mapper/alias (ie.
>> "raw104:mapper/raw99p1"). Once that file was created, I modified
>> /etc/udev/udev.permissions with all of my raw devices, and what
permissions
>> i want them set to on creation/binding of the raw devices, and then
run
>> /etc/init.d/raw start. Once that's all performed, ASM see's the
devices as
>> /dev/raw/raw104 as a single device, and is able to import it.
>>
>> Let me know if this information helps you at all, or even if
you'd like
>> to ask any questions to get you moving.
>>
>> Good Luck!!
>> Mike Kershaw
>>
>> On 1/11/07, LOPEZ DIAZ, JORGE wrote:
>>
>> Hello every one,
>>
>>
>>
>> I'm trying to setup ASM in a two nodes RAC cluster 10.2 over
SLES10. I
>> want to use multipath (with a EMC SAN CX500). Multipath is running
ok, as I
>> can see all LUN's defined. But from runInstaller, I can??t see any of
the
>> devices /dev/dm-xx than multipath has generated. I change definition
of path
>> to "/dev/dm-*" and "/dev/disk/by-name/*" with no results. It's
supossed that
>> raw devices are not necessary.
>>
>>
>>
>> So, I defined in /etc/raw 12 equivalences to dm-xx devices, but
after
>> restart servers only 9 raw names appears in /dev/raw, and from
runInstaller,
>> only 6 of them appears as candidates with path "/dev/raw/*". For
SLES, all
>> dm-xx devices are availables.
>>
>>
>>
>> No one of this devices has partitions defined.
>>
>>
>>
>> Any suggestion?
>>
>>
>>
>> This time are real servers, not vmware, for migrate a 9.2 RAC
database to
>> these new servers.
>>
>>
>>
>> Any suggestion?
>>
>>
>>
>>
>>
>>
>>
>> --
>> To unsubscribe, email: suse-oracle-unsubscribe@(protected)
>> For additional commands, email: suse-oracle-help@(protected)
>> Please see http://www.suse.com/oracle/ before posting
>>
>>
>>
>> --
>> To unsubscribe, email: suse-oracle-unsubscribe@(protected)
>> For additional commands, email: suse-oracle-help@(protected)
>> Please see http://www.suse.com/oracle/ before posting
>>
--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting
