Using Serviceguard Extension for RAC Version A.11.20 - (August 2011)
Step 2 remains the same. Logical volumes are prepared for the new disks in the same way.
In step 3, switch the volume group back to shared mode, using SNOR, and export the VG across
the cluster, ensuring that the right ownership and access rights are assigned to the raw logical
volumes. Activate the volume group, and restart ASM and the database(s) using ASM-managed
storage on all nodes (they are already active on node A).
SG/SGeRAC Support for ASM on HP-UX 11i v3
Overview
Support for ASM with SG/SGeRAC commences with SGeRAC A.11.17.01 on HP-UX 11i v3.
SGeRAC support ASM where the member disk groups are either logical volumes managed by HP
Shared Logical Volume Manager (SLVM) or raw disks/disk array logical units(LUs).
A new I/O infrastructure that enables the native built-in multipathing functionality is introduced in
HPUX 11i v3. This feature offers users a continuous I/O access to a LUN or disk if any of the paths
fails. This feature is enabled in the operating system by default. In addition, new DSF(device special
file) format is introduced in this operating system. An example of new DSF is /dev/disk/disk1,
compare to the legacy DSF, /dev/rdsk/cxtydz.
Please note that it has been possible to set up Oracle databases using ASM on HP-UX from the
time Oracle 10g became available on HP-UX, using the following configurations that do not require
SG/SGeRAC:
• Non-clustered single instance Oracle.
• Oracle single instance and RAC databases running in a pure Oracle clusterware environment.
The following requirements/restrictions apply to SG/SGeRAC (A.11.17.01 or later) support
of ASM (summarized in Table 4):
Table 4 ASM support with SG/SGeRAC A.11.17.01 or later
Not SupportedSupported
Oracle single instance database, with or without Oracle
clusterware
Oracle RAC database
CVM Logical Volumes as ASM Disk Group MembersSLVM Logical Volumes as ASM Disk Group Members
Single instance Oracle database with ASM managed
storage running in Serviceguard cluster
ASM configurations on SGeRAC using SGeRAC
A.11.17.01 or later, and Oracle 10g R2 RAC
Single instance Oracle database with ASM-managed
storage in SGeRAC configuration wherein SGeRAC
provides node membership to Oracle Clusterware
ASM configurations on SGeRAC using SGeRAC
A.11.17.01 or later, and 11g R1 RAC
Maximum SGeRAC cluster size for ASM configurations is
16
SGeRAC Toolkit3 framework based on Multi-Node Package
(MNP) /Simple Package Dependency to manage ASM
configurations on SGeRAC up to a maximum cluster size
of 16
Raw disks/disk array LUs as ASM Disk Group Members
ASM over SLVM
SGeRAC support for ASM-over-SLVM continues in HPUX 11i v3. SGeRAC 11.17.01 or later is
required for ASM-over-SLVM configurations on HP-UX 11i v3.
SG/SGeRAC Support for ASM on HP-UX 11i v3 73