http://www.dba.5341.com/
http://www.dba.5341.com/
Hello Oliver,
The target is not to
use raw devices, just block devices. I’ll try the udev way indicated by Clemens.
Thanks.
|
|
Jorge López Díaz |
|
|
|
De: Oliver Gehlert
[mailto:funklover4u@yahoo.de]
Enviado el: lunes, 02 de octubre
de 2006 12:09
Para: LOPEZ DIAZ, JORGE
CC: suse-oracle@suse.com
Asunto: AW: [suse-oracle] ASM and
block devices
Hi,
did you add the devices to /etc/raw?
Regards
Oliver
----- Ursprüngliche Mail
----
Von: Fabrizio Magni <fabrizio.magni@gmail.com>
An: "LOPEZ DIAZ, JORGE" <jorge.lopez@carm.es>
CC: suse-oracle@suse.com
Gesendet: Samstag, den 30. September 2006, 20:47:23 Uhr
Betreff: Re: [suse-oracle] ASM and block devices
Jorge,
has the oracle user the right permission on the devices?
Are the device "clean"?
Go with a dd (with the oracle user) to make sure of both:
dd if=/dev/null of=your_device_here bs=4096k count=10
The easiest way to be able to access the devices is to add the oracle
user at the "disk" group.
Regards
Fabrizio
PS: ASM_DISKSTRING can be set before creating the ASM or even after.
You can always add the devices after the ASM instance is running.
LOPEZ DIAZ, JORGE wrote:
> Hi Fabrizio,
>
>
>
> When runInstaller ask for select candidate disks, there is a buttom to
change where to look at. If I specify '/dev/sd*' to try to use block devices
the list is empty. If I specify '/dev/*' the list has two lines: /dev/random
and /dev/null.
>
>
>
> Perhaps I must specify ASM_DISKSTRING before to lunch runInstaller.
>
>
>
>
>
> Jorge López Díaz
>
> ________________________________
>
> De: Fabrizio Magni [mailto:fabrizio.magni@gmail.com]
> Enviado el: jueves, 28 de septiembre de 2006 14:21
> Para: LOPEZ DIAZ, JORGE
> CC: suse-oracle@suse.com
> Asunto: Re: [suse-oracle] ASM and block devices
