Best Practices for SGeRAC and Oracle RAC on HP-UX 11i, March 2009

16
The preferred storage configuration, with a minimum of two ASM disk groups per database, is as
follows:
• VG/local FS for Oracle Clusterware home
• VG/local FS for Oracle home
• Raw devices for OCR and Voting Disk (can also use SLVM VG)
• For each RAC database
o Two ASM disk groups
o One for database data and the other for flash recovery
ASM over SLVM
SGeRAC supports ASM over SLVM. The ASM disk groups members must be raw logical volumes (LV)
managed by SLVM.
• ASM supports
o Data files, control files, online and archive redo log files, and backup files.
• ASM does not support
o Oracle binaries, trace files, audit files, alert logs, export files, tar files, core files
o Oracle cluster registry devices (OCR) and quorum device (Voting Disk)
o Application binaries and data
The preferred storage configuration, with a minimum of two ASM disk groups per database, is as
follows:
• VG/local FS for Oracle Clusterware home
• VG/local FS for Oracle home
• SLVM VG for OCR and Voting Disk
• For each RAC database
o Two ASM disk groups, each residing in its own SLVM VG
o One for database data and the other for flash recovery
Online changes support the same as SLVM. Therefore, changes through SNOR require deactivation
and halting of applications using the shared volume group on all but one node. An I/O timeout for
the shared logical volumes must be configured.
Serviceguard packages
In the combined software stack, SGeRAC provides the following to Oracle Clusterware (OC) and
RAC:
• Cluster membership to CSS
• Clustered storage to meet the needs of OC and RAC database instance
Oracle Clusterware manages the following:
• Database and associated resources (database instance, services, VIP, listener, etc…)
• ASM instance, when configured.