Reference Architecture: Consolidating Oracle Databases with Secure Resource Partitions in a Serviceguard Cluster Whitepaper

6
binaries and libraries but might run with different configuration/profiles, usually by specifying a
different configuration file for each instance
Pros:
– Single installation to patch
– Little extra disk space consumption for additional instances
Cons:
– Single version of application software
– Inflexible installation
– Inflexible update path when updating binaries all applications will be affected
 Multi-installation/Multi-instance—You can install multiple copies (and potentially multiple versions)
of the application in different locations of the file system. These types of applications are typically
self-contained under a single directory. In addition to installing the software in multiple locations,
you can run multiple instances of the application at the same time.
Pros:
– Installation of multiple versions of application
– Flexible installation
– Flexible updates
Cons:
– More disk space consumption for each installation
– Additional installations to patch
Oracle Database Server installation and execution can be deployed in both of the scenarios, which
enables the administrator to have great flexibility and choice for their deployment.
When you deploy Oracle Database Server with Secure Resource Partitions, HP recommends using the
Multi-installation/Multi-instance architecture. Because each SRP can operate as an isolated execution
environment for that application, you must keep both the Oracle software and database files
segregated from each SRP. Using this architecture enables you to easily isolate the Oracle installation,
database files, and configuration by simply locating them under the SRP private directory
(/var/opt/<SRP Name>/…). Deploying each SRP/database instance with its own software
installation provides an isolated administrative domain that enables you to manage the Oracle
software and patch level without affecting other Oracle installations on the system, closely emulating
standalone deployments. Installing Oracle within the SRP also simplifies cloning the SRP for
Serviceguard because the database software is part of the SRP file set, eliminating the issue of
managing the database as a system dependency.
Oracle does not currently support RAC deployed within an SRP.
Database storage
Files store all Oracle data, index, configuration, and log files for this reference architecture. Although
you can use a device-based IO such as Raw IO or Oracle ASM, this white paper does not discuss
them. All files will be stored under the SRP private directory structure. Using this configuration serves
multiple purposes:
 Simple security—Because the default SRP compartment rules restrict other SRPs from accessing the
SRP private directory, no additional compartment rules are required.
 Modular design—Placing all SRP-related files under a common directory makes it easier to clone or
migrate an SRP and its applications to another system.
Database files will be stored in the /var/hpsrp/<SRP>/u02 directory. While this architecture uses a
single mount point for all database and log files, you might want to split Oracle files across multiple
mount points. In this case, place all mount points in the /var/hpsrp/<SRP> directory to maintain the