“floating” IP address. This floating IP address is called as package IP in Serviceguard terms. The floating IP address is one that is defined for exclusive use by the database as its networking end point 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 it is this name that will be used as the database’s hostname within the EBS topology configuration.

From the EBS APPS Tier point of view, the database failover from one machine to the other does not alter the single network end point at which it connect for service. As there is no change in the networking end point, no special reconfiguration of applications is required to handle the database failover sequence.

Much of the process of setting up the virtual hostname environment for the EBS database tier is automated during the installation process by using the –servernameflag with the RapidInstall EBS Installer command. Details on this command option can be found in the Oracle Applications Release 12 installation guide.

As an example, to install the database tier with the virtual hostname ebs database, the RapidInstall command used to install the database tier needs to be started with the –servername ebsdatabase command line option. This will install the database product components, build the appropriate configuration files and file system directory layout automatically and use 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) simplifies administration of Oracle EBS DB Tier related files by allowing administrator to reference disk groups rather than individual disks and files. It provides functionalities like managing disk groups, disk redundancies, and allows management of database objects without specifying mount points and filenames.

Currently Oracle EBS DB Tier Rapid installation allows user to house the database in either shared file system or local file system. Automatic Storage Management is currently not supported using EBS DB Tier Rapid Install.

To support ASM for EBS DB Tier, Migrate from non-ASM storage to ASM storage. The following steps are for migrating EBS DB from Non-ASM storage to ASM storage:

NOTE: While performing the migration procedure, a scheduled downtime is needed for the application.

1.Halt the SGeEBS APPS Tier Packages on all nodes which are currently using DB Tier package whose database storage needs to be migrated.

2.Ensure that approximately 200GB free disk space is needed to create the ASM disk groups for EBS database.

3.Perform the migration procedure as per the Oracle document. "Steps To Migrate/Move a Database From Non-ASM to ASM [ID 252219.1]".

NOTE: Refer to the latest Oracle document available in Oracle support website.

4.Set up the ASM and EBS DB packages with ASM. For details, see the section “Supporting Oracle ASM instance and Oracle database with ASM” (page 26) in this user guide.

58 Using the Oracle Toolkit in an HP Serviceguard Cluster