Oracle rac 10g

[nightwich]

Hi All !!

I have the following situation.

O.S -> HP-UX B.11.11
ServiceGuard -> A.11.16.00
erviceguard Extension for RAC -> A.11.16.00

1 - The oraclware do all the work related to Database ( shutdown startup ip's etc.. ) so I do not need Service guard package configuration for that.

2 - To use oracle rac we need to have a VG em shared mode

3 - at start up we need first to have de VG accessible and then start oraclware

4 - at shutdown we need first stop oraclware then deactivate Shared VG

5 - for this we have the following scripts at /sbin/rc3.d:

- S800cmcluster -> /sbin/init.d/cmcluster
- S950actrac.vg -> /sbin/init.d/actrac.vg
- S960init.crs -> /sbin/init.d/init.crs

*S960init.crs (iniciate the oraclware )
*S800cmcluster ( start the custer )
more S950actrac.vg :
/usr/sbin/vgchange -a s /dev/yyy
/usr/sbin/mount /dev/yyy/xx /ora_arch/xx

6 at /sbin/rc2.d we have:

- K001init.crs -> /sbin/init.d/init.crs
- K002desrac.vg -> /sbin/init.d/desrac.vg
- K003cmcluster -> /sbin/init.d/cmcluster

My problem is when I run this scripts manually, all run good. Although when I do a reboot I get the following error before start to execute the shutdown scripts:

/dev/ORARAC/arch_22:
vgchange: Failed to notify clvm daemon about volume group deactivation - Device busy
Couldn't deactivate volume group "/dev/ORARAC":
Device busy



System shutdown in progress
___________________________

Stop Oracle Cluster Ready Services .... OK
................................... OK
Stop Highly Available cluster ....... OK


Please advice

Regards

[Steven E. Protter]

Shalom,

Service Guard package scripts do the following:

1) Activate the volume group for the node.
2) Kick a startup script for RAC.

In this case the volume group activation failed.

See /var/adm/syslog/syslog.log

Try activating the volume group manually and see what error you get.

My guess is the volume group is active in the wrong mode on the other node. A cmhaltnode command might be needed, but that will lead to a service interuption.

SEP

[Shardha]

Dear,

When you need to put a vg activation under cluster management you need to put the vg as follows (exclusive mode)

vgchange -a e

also you need to modify the file

The /etc/lvmrc File
When using volume groups within MC/ServiceGuard, the volume groups should not be activated automatically at boot time. MC/ServiceGuard will activate a package's defined volume group when the package is started on the node where the package is running.
Remember, only one node can activate a volume group at a time.
The default behavior of the boot process is to activate all known volume groups at boot time.
This needs to be changed for cluster marked volume groups. To modify the default behavior
at boot time, edit /etc/lvmrc and make the following changes:
â ¢ Set AUTO_VG_ACTIVATE=0. This will turn off the automatic activation of all volume
groups at boot time.
â ¢ Specify selected volume groups to be activated at boot time in the custom_vg_activation
routine. All volume groups (except vg00) to be activated when the system boots should
be listed here. These volume groups do not include cluster marked volume groups.

Shardha

[nightwich]

Hi Steven and Sardha.

Thanks for the fast reply.

@Sardha this is ORACLE RAC the VG must be in shared mode, so I can't activate de VG as you sugest.

@Steven I already resolve this issue, i configure a package just to start oraclware, mount/umount LV's and activate/deactivate VG.

Regards..