SG, LVM

[shashi kanth]

I have 3-node SG11.18 Oracle10g Fail-over setup. Oracle binary and database files are on the top of LVM. The instance is running on the primary node.

I stopped the instance in primary node, and trying to start in other 2 nodes. I am getting the bellow error when i am trying to start in other two nodes.

########### Node "cabrio": Starting package at Tue Jun 24 12:36:28 IST 2008 ###########
Jun 24 12:36:28 - Node "cabrio": Activating volume group cookeddg with exclusive option.
vgchange: Volume group "/dev/cookeddg" does not exist in the "/etc/lvmtab" file.
ERROR: Function activate_volume_group
ERROR: Failed to activate cookeddg
Jun 24 12:36:28 - Node "cabrio": Deactivating volume group cookeddg
vgchange: Volume group "/dev/cookeddg" does not exist in the "/etc/lvmtab" file.
Jun 24 12:36:28 - vgchange -a n cookeddg failed, trying again.
vgchange: Volume group "/dev/cookeddg" does not exist in the "/etc/lvmtab" file.
Jun 24 12:36:29 - vgchange -a n cookeddg failed, trying again.
vgchange: Volume group "/dev/cookeddg" does not exist in the "/etc/lvmtab" file.
ERROR: Function deactivate_volume_group
ERROR: Failed to deactivate cookeddg

########### Node "cabrio": Package start failed at Tue Jun 24 12:36:30 IST 2008 ###########




Any one tell me what i am missing ?

Thank you .

[Torsten.]

All the VGs are not included in /etc/lvmtab.

Did you vgimport them while you configure the cluster?

[shashi kanth]

I have created the VG in primary node and installed Oracle before SG cluster formed.

With HP LVM, how other 2 nodes can see the VG which resides in primary node ?

Do i need to copy the /etc/lvmtab from primary to other 2 nodes ?

[Torsten. · Accepted solution]

Do NOT copy /etc/lvmtab.

See

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=180447

and scroll down to step 6 in Christopher McCray's post.

[Kenan Erdey]

Hi,

I am attaching a good document that will help you.

Kenan.

[Duncan Edmonstone]

I am suspicious of the naming of your volume group - anything ending in "dg" could well be a VxVM disk group rather than a LVM volume group. It might just be a naming thing, but can you confirm that on the primary node that cookeddg is a LVM volume group and not a VxVM disk group?

HTH

Duncan

[shashi kanth]

I am using HP LVM only.


Now i have another problem, I am trying to import the map file in the 2nd node, I am getting the bellow error.

# vgimport -v -s -m /cookeddg.map cookeddg
Beginning the import process on Volume Group "cookeddg".
vgimport: Minor number of /dev/cookeddg/group is not unique. /dev/rawdg/group has the same minor number.



There is already another VG which resides in 2nd node. The minor number of that VG, and minor number "cookeddg" in primary node are same.


Now what i have to do ?

[Duncan Edmonstone]

Just use another minor number. Minor numbers don't actually have to match between servers (although it's good practice to)

It would be better to maybe change the minor number of the rawdg if you can (using vgexport/vgimport), although again be careful if this volume group is present on other systems as well.

Incidentally - why are you using the naming convention ....dg? That's potentially going to confuse people. The de facto standard with LVM is either vg.... or ....vg

HTH

Duncan