3.7.0 HP StorageWorks MxDB-Oracle-HiAv installation and administration guide HP MxDB-Oracle-HiAv for Linux (AG513-96009, June 2009)

files that need to be identical, there is only one copy, not several, to maintain.
However, with shared Oracle homes, it is not possible to do a rolling upgrade but
the down time is typically very brief.
With this shared environment, care must be taken so that oracle users and group
identifiers are consistent across servers. Otherwise, user “oracle” with user id500
on server 2 will not have ownership to the shared filesystem if on the installing server,
server 1, user “oracle” is user id 501. In a shared filesystem, the uids and gids matter,
not the names. Obviously, mount points must be named identically to avoid having
an inconsistent set of paths for Oracle Home and oradata.
HP Scalable NAS filesystems can support either direct asynchronous I/O or
synchronous buffered I/O. The determining factor is how the filesystem is mounted
in the cluster (direct I/O with the “DBOptimized” option or buffered I/O with the
“Standard” option). It is important to use the Standard option for $ORACLE_BASE
and the DBOptimized option for Oracle data files. Chapter 2 describes how to do
this to maintain OFA standards. Direct and asynchronous I/O is actually provided
by the Linux operating system, a kernel-based implementation with the supported
Linux releases.
Naming conventions
The associations among the Virtual Oracle Server, service monitor, Database Instance,
and Database Name can become confusing if certain naming conventions are not
followed. It is generally best practice to use the following naming scheme:
• The names of the database and the ORACLE_SID should be the same, including
case sensitivity.
• The service monitor and the database should have the same name. (The name is
specified when you place the database under MxDB-Oracle-HiAv control.)
• Because the Virtual Oracle Service name must be entered in DNS, selecting the
name is typically not entirely under DBA control. The Database Administrator
may need to negotiate with the System or Network Administrator to agree on a
name that makes sense for the site.
Whenever possible, HP recommends that the Virtual Oracle Service name consist
of the database name followed by the domain suffix. For example, if the database
instance, database name, and service monitor are all called PROD and the domain
suffix is customer.com, the Virtual Oracle Service name would be PROD.custom-
er.com.
MxDB-Oracle-HiAv installation and administration guide 11