Understanding the HP Serviceguard Extension for Oracle E-Business Suite (SGeEBS)

Figure 2: Failover of the Oracle EBS APPS tier package

Dependency between APPS and DB packages

There exists a complex dependency between the APPS and DB packages of SGeEBS. The DB

package should know the name of the APPS package and vice versa. The proper sequence of starting

the EBS packages is DB first and then APPS. If the APPS package is started first, the first step in the

startup sequence is to ensure that the DB package is running somewhere in the cluster. Since the APPS

tier requires that the DB tier be active in order for EBS to function correctly, SGeEBS ensures that the

EBS APPS package only ran if the DB package was up and running and if it is not found running or if

it is in maintenance mode, the APPS package startup will be aborted. Serviceguard package

dependency should not be put between APPS and DB packages.

The proper sequence of bringing down the EBS packages is APPS package first and then the DB

package. If DB package is brought down when the APPS package is up and running, the APPS

package also will be brought down in the shutdown sequence of the DB package. The APPS package

will be halted even if it is in maintenance mode.

The failover scenarios of EBS packages are different from operator initiated start and stop operations.

There is no issue in failing over the APPS package when the DB package is running on any node of

the cluster. Similarly, if the DB package fails over the APPS package will not be brought down.

The APPS package can survive for some time without the DB package. During this time, you will see

one or more of the following messages in the package log file.

*** EBS APPS MONITOR *** Concurrent Processing is failing

*** EBS APPS MONITOR *** Fulfillment Server is failing

Resilient Networking

Serviceguard

Monitoring

Shared Storage Disk

Array Subsystem

sg-serv 1

ebsdatabase

DB package

DB Tier Programs

and Data

Apps Tier Programs

and Data