What are the meanings of the target and state status values?

You enter the following command:
crsctl status resource MyApp
You get this output:
NAME=MyApp

TYPE=cluster_resource TARGET=ONLINE STATE=ONLINE on RACNODE4
MyApp is a policy-managed resource using a server pool with two nodes called RACNODE3 and
RACNODE4 and has a cardinality of 1.
What are the meanings of the target and state status values?

You enter the following command:
crsctl status resource MyApp
You get this output:
NAME=MyApp

TYPE=cluster_resource TARGET=ONLINE STATE=ONLINE on RACNODE4
MyApp is a policy-managed resource using a server pool with two nodes called RACNODE3 and
RACNODE4 and has a cardinality of 1.
What are the meanings of the target and state status values?

A.
MyApp is currently active on RACNODE4 and is meant to be active only on RACNODE4.

B.
MyApp is meant to be active, is currently active on RACNODE4, but the Grid Infrastructure may
start MyApp on RACNODE3 due to failovers.

C.
MyApp is active on RACNODE4 and was manually started.

D.
MyApp should also be online on RACNODE3 because it is a cluster_resources type that must
be active on at least two nodes in the cluster, thereby overriding the CARDINALITY attribute.

Explanation:
Resource Attributes
NAME
A case-sensitive alphanumeric string that names the resource. Oracle recommends a naming
convention that starts with an alphanumeric prefix, such as myApache, and complete the name
with an identifier to describe it.
A resource name can contain any platform-supported characters except the exclamation point (!)
and the tilde
(~). A resource name cannot begin with a period (.) nor with the string ora.
TYPE
The type of resource indicated when you create a resource. This attribute is required when
creating a resource.
Local resource: Instances of local resourcestype name is local_resourcerun on each server of
the cluster. When a server joins the cluster, Oracle Clusterware automatically extends local
resources to have instances tied to the new server. When a server leaves the cluster, Oracle
Clusterware automatically sheds the instances of local resources that ran on the departing server.
Instances of local resources are pinned to their servers; they do not fail over from one server to
another.
Cluster resource: Cluster-aware resource typestype name is cluster_resourceare aware of the
cluster environment and are subject to cardinality and cross-server switchover and failover.
TARGET
An internal, read-only attribute that describes the desired state of a resource. Using the crsctl start
resource_name or crsctl stop resource_name commands, however, can affect the value of this
attribute.
STATE

An internally-managed attribute that reflects the current state of the resource as reported by
Oracle Clusterware. The state of a resource can be one of the following:
ONLINE: The resource is online and resource monitoring is enabled (see CHECK_INTERVAL).
OFFLINE: The resource is offline and only offline resource monitoring is enabled, if configured
(see OFFLINE_CHECK_INTERVAL).
INTERMEDIATE: The resource is either partially online or was known to be online before and
subsequent attempts to determine its state have failed; resource monitoring is enabled (see
CHECK_INTERVAL).
UNKNOWN: The resource is unmanageable and its current state is unknown; manual intervention
is required to resume its operation. A resource in this state is not monitored.
Oracle Clusterware Administration and Deployment Guide
11g Release 2 (11.2)



Leave a Reply 1

Your email address will not be published. Required fields are marked *


L. Zhu

L. Zhu

A is wrong. Myapp can run on node 3
B is right. node 3 and 4 are available for myapp and because cardinality is 1 so it is on node 4
C is wrong. not manually
D is wrong. not overriding cardinality attribute

So B is correct.