HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)

# cmrunpkg <dbpkg_name>
Check the package status using cmviewcl. Verify that the database instance is running. Repeat
these steps for each database instance.
ECMT Oracle Toolkit Maintenance Mode
To place the single-instance ECMT Oracle toolkit package in maintenance mode, set the package
attribute MAINTENANCE_FLAG to ‘yes’ . Also, a file named ‘oracle.debug’ must exist in the package
directory.
In a coexistence environment, the single-instance database goes into toolkit maintenance mode if
any of the following condition is met:
1. If the MAINTENANCE_FLAG is set to ‘yes’ in the ECMT package configuration for single-instance
Oracle and if oracle.debug file exists in the package directory.
2. If the SGeRAC OC MNP package is put in toolkit maintenance mode by creating an oc.debug
file in the SGeRAC OC MNP package directory.
Supporting EBS database Tier
ECMT Oracle toolkit has been enhanced to support the packaging of EBS database Tier. High
availability for the EBS database tier is achieved using the same technique that many standalone
Oracle database implementations with Serviceguard have used in production for a considerable
time.
NOTE: ECMT Oracle Toolkit can be used only to configure the EBS Database Tier and to configure
the EBS APPs Tier, you must purchase SGeEBS.
You can use re-locatable storage devices and a special “floating” IP network address, to failover
the database from one physical server to another within the Serviceguard cluster while retaining
the same outward appearance to applications.
From a network communications point of view, the Oracle database is not configured to bind to
the network address associated with the actual physical server but rather to a specially-reserved
“floating” IP address. This floating IP address is called package IP in Serviceguard terms. The
floating IP address is defined for exclusive use by the database. It is the networking end point of
the database and is normally included in the Domain Name Service so that the database can be
located by its applications. The symbolic name that is associated with the floating IP address is
the “virtual hostname” and this name is used as the database’s hostname within the EBS topology
configuration.
From the EBS APPS Tier point of view, the database failover does not alter the single network end
point from one machine to the other when connected for service. There is no change in the
networking end point, therefore no special reconfiguration of applications is required to handle
the database failover sequence.
Use the –servername flag with the RapidInstall EBS Installer command, to automate the process of
setting up the virtual hostname environment for the EBS database tier during the installation process.
For more information, see the Oracle Applications Release 12 installation guide.
For example, to install the database tier with the virtual hostname ebs database, you must start the
RapidInstall command used to install the database tier with the –servername ebsdatabase command
line option. This installs the database product components, automatically builds the appropriate
configuration files and file system directory layout, and uses the virtual hostname ebsdatabase in
place of the actual server hostname on which the install was run.
Oracle ASM Support for EBS DB Tier
Automatic Storage Management (ASM) allows administrator to reference disk groups rather than
individual disks and files, therefore simplifies administration of Oracle EBS DB Tier related files. It
62 Using the Oracle Toolkit in an HP Serviceguard Cluster