Operating System - HP-UX
1748140 Members
3445 Online
108758 Solutions
New Discussion юеВ

volume group not activated

 
shankar!
Frequent Advisor

volume group not activated

Hi,

I have two node cluster srv1 srv2, the cluster and package is up and running. The shared volumes on srv1 mounted well, but not on srv2. It shows,

srv2:root> vgdisplay
--- Volume groups ---
VG Name /dev/vg0
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 10
Open LV 10
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 4384
VGDA 4
PE Size (Mbytes) 16
Total PE 8748
Alloc PE 4454
Free PE 4294
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg02".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg01".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg03".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg04".
You have mail in /var/mail/root

I tried,
srv2:root> vgchange -a s vg01
vgchange: Activation mode requested for the volume group "/dev/vg01" conflicts with configured mode.
srv2:root> vgchange -a e vg01
vgchange: Activation of volume group "/dev/vg01" denied by another node in the cluster.
Request on this system conflicts with Activation Mode on remote system.
srv2:root> vgchange -a y vg01
vgchange: Activation mode requested for the volume group "/dev/vg01" conflicts with configured mode.

Due to this, the oracle server is not running on srv2 server. can someone help us on this?

Thanks
-shankar
18 REPLIES 18
Pete Randall
Outstanding Contributor

Re: volume group not activated

shankar!
Frequent Advisor

Re: volume group not activated

Thanks for your speedy response. But that link seems not much help to our situation.

thans
-shankar
Torsten.
Acclaimed Contributor

Re: volume group not activated

First you should check the cluster status and vgdisplay output on the other node to get the current status and configuration. Inspect the cluster config as well to know about what mode to use.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
smatador
Honored Contributor

Re: volume group not activated

Hi,

Change the flag cluster to no, and active it on exclusive
# vgchange -c n /dev/vg01
# vgchange -a e /dev/vg01
# vgchange -a y /dev/vg01
You could like that, activate the vg in local.

Hope it helps
likid0
Honored Contributor

Re: volume group not activated

Hi,

Check in your first node where the vgs are active if they are in shared mode, do:

#vgdisplay -v /dev/vgshared | grep "VG Status"
VG Status available, shared,master

You should get out like above, if you don't then looks like it isn't activated in shared mode. If that's the case you should do, on the first node with SG runing:

/usr/sbin/vgchange -c cluster -S sharable vg_name

and then:

vgchange -a s vg_name

and finally on the second node:

vgchange -a s vg_name

Windows?, no thanks
shankar!
Frequent Advisor

Re: volume group not activated

Here is the cluster status and vgdisplay output

srv1:root> cmviewcl -v

CLUSTER STATUS
hprac up

NODE STATUS STATE
srv1 up running

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/1/2/0 lan0
PRIMARY up 0/3/1/0/4/0 lan1
PRIMARY up 0/3/1/0/5/0 lan2

PACKAGE STATUS STATE AUTO_RUN NODE
beserv_pkg up running enabled srv1

Policy_Parameters:
POLICY_NAME CONFIGURED_VALUE
Failover configured_node
Failback manual

Script_Parameters:
ITEM STATUS MAX_RESTARTS RESTARTS NAME
Subnet up 172.16.0.0

Node_Switching_Parameters:
NODE_TYPE STATUS SWITCHING NAME
Primary up enabled srv1 (current)
Alternate up enabled srv2

NODE STATUS STATE
srv2 up running

Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/1/2/0 lan0
PRIMARY up 0/3/1/0/4/0 lan1
PRIMARY up 0/3/1/0/5/0 lan2


srv1:root> vgdisplay
--- Volume groups ---
VG Name /dev/vg0
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 4384
VGDA 4
PE Size (Mbytes) 16
Total PE 8748
Alloc PE 7194
Free PE 1554
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

VG Name /dev/vg01
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 6
Open LV 6
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 35004
VGDA 2
PE Size (Mbytes) 8
Total PE 17499
Alloc PE 15256
Free PE 2243
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

VG Name /dev/vg02
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 4
Open LV 4
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 35004
VGDA 2
PE Size (Mbytes) 8
Total PE 17499
Alloc PE 16375
Free PE 1124
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

VG Name /dev/vg03
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 4
Open LV 4
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 35004
VGDA 2
PE Size (Mbytes) 8
Total PE 17499
Alloc PE 8125
Free PE 9374
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

VG Name /dev/vg04
VG Write Access read/write
VG Status available, exclusive
Max LV 255
Cur LV 4
Open LV 4
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 35004
VGDA 2
PE Size (Mbytes) 8
Total PE 17499
Alloc PE 8381
Free PE 9118
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

thanks
-shankar
Torsten.
Acclaimed Contributor

Re: volume group not activated

The status of all VGs are available, exclusive from server1, so you cannot activate them from the other server until the packages are stopped.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
shankar!
Frequent Advisor

Re: volume group not activated

yes, the volumes are not sharable. I did the following on the first node (srv1),

srv1:root> /usr/sbin/vgchange -c hprac -S sharable /dev/vg01
Usage: vgchange
{-a Availability -q Quorum [-l] [-p] [-s] [VolumeGroupName... ]}
{[-S shareable] -c cluster VolumeGroupName}
{[-P parallel_nomwc_resync_count]}
"cluster": Bad value supplied. Legal values are "yn".

any help?
thanks
shankar!
Frequent Advisor

Re: volume group not activated

so, should i stop the cluster on both nodes using cmhaltcl and then execute above commmands and then run cluster?

thanks