You approach seems incorect.
The devices are shared right ? So why do you re-create partitions on
the server B, after you have created them and prepared your devices on
Server A ?
The procedure should be:
Server A
fdisk /dev/sde
-> create partition
fdisk /dev/sdd
-> create partition
/etc/init.d/oracleasm createdisk ... /dev/sde1
/etc/init.d/oracleasm createdisk ... /dev/sdf1
Server B
fdisk /dev/sde
"p" for print, you should see the partition created
"w" to rewrite it, and refresh in memory partition table
fdisk /dev/sdf
"p" for print, you should see the partition created
"w" to rewrite it, and refresh in memory partition table
/etc/init.d/oracleasm scandisks
/etc/init.d/oracleasm listdisks
-> should show your marked devices
Use dbca to create diskgroups.
--
Christo Kutrovsky
Senior Database/System Administrator
The Pythian Group - www.pythian.com
I blog at http://www.pythian.com/blogs/
On 5/10/06, oracle sos <sosoracle@xxxxxxxxx> wrote:
>
> Hello,
>
> Here is what I am trying to do.
>
> two servers: Let's call A and B in short
> ASMLib 1.0 installed and configured on server A and B
> two shared raw devices /dev/sde and /dev/sdf
>
> Server A
> create 1 partition on each of them, /dev/sde1 and /dev/sdf1, using fdisk
> command
> /etc/init.d/oracleasm createdisk VOL1 /dev/sde1
> /etc/init.d/oracleasm createdisk VOL2 /dev/sdf1
> /etc/init.d/oracleasm listdisks (shows VOL1 and VOL2)
> run dbca to configure ASM: DATA_1 --> VOL1 and DATA_2 --> VOL2
>
> Server B
> use sfidk -R to create 1 partition on /dev/sde and /devsdf
> /etc/init.d/oracleasm scandisks <---- want to give server B a notice of
> VOL1 and VOL2 ASM diskgroups
> /etc/init.d/oracleasm listdisks <----- show nothing ????
> run dbca to configure ASM: <--- can't see any asn disk group(s)
>
> Does anyone can point it out to the missing/wrong procedure of the above
> configuration?
>
> If I use /etc/init.d/oracleasm createdisk VOL1 /dev/sde1 on Server B, I
can
> see the diskgroup while configuring ASM, but I got,
>
> ora-15003, Disk Group DATA_1 already mounted in another lock name space
>
> *****************************
>
> Does anyone have any idea of how to make that working? Many thanks for
all
> the help.
> Cindy
--
Christo Kutrovsky
Senior Database/System Administrator
The Pythian Group
