Oracle Clusterware Diagnosis - Expert Oracle RAC Performance Diagnostics and Tuning - page 568

Table 16-5. EVMD actions

Action Priority Function

Error 500 No response is received for the action sent

Transition 300 The event is in a state change process. Normally the action is received when a resource

or service is initially started, stopped, or failing over.

Down 200 Indicates that the resource or service is currently down

Running 300 Indicates that the service or resource is currently in execution state. This state is

normally seen in cluster services or applications managed by the Oracle Clusterware,
for example, CRS

Up 200 Indicates that the service or resource specified is up.

Imstop 200 Indicates an HA service stop action

relocatefailed 300 Indicates an attempt to relocate a service or resource from one node to another;

however, such relocation attempt has failed. This action normally follows other actions
such as “imstop” or “stopped”

Stopped 300 Indicates that the application has completely stopped execution

Grid Plug and Play
Starting with Oracle Clusterware 11g Release 2, Oracle has introduced a new feature called Grid Plug and Play, which
is managed by the Grid Plug and Play daemon (GPnPD). During installation, Oracle creates and makes copies of the
Oracle universal installer, called the GPnP profile. The profile is stored in the GPnP cache on all nodes in the cluster.
Unless the profile is changed using of the client interfaces, the data in the cache should be identical on all nodes in the
cluster. The Profile Sequence number identifies the version of the profile.
Figure 16-4 is a snapshot of the GPnP profile, which contains bootstrap information that is required in order to
form the cluster. The following is a list of information found in the profile:

• Profile sequence

• Cluster UID

• Cluster name

• Host network

• CSS profile

• ASM profile

• Wallet information, such as the public and private RSA keys