Faq Rac1
Faq Rac1
Faq Rac1
Manages cluster node membership and runs as the oracle user; failure of this process results in
cluster restart.
The crs process manages cluster resources (which could be a database, an instance, a service, a
Listener, a virtual IP (VIP) address, an application process, and so on) based on the resource's
configuration information that is stored in the OCR. This includes start, stop, monitor and
failover operations. This process runs as the root user
This process monitor the cluster and provide I/O fencing. OPROCD performs its check, stops
running, and if the wake up is beyond the expected time, then OPROCD resets the processor and
reboots the node. An OPROCD failure results in Oracle Clusterware restarting the node.
OPROCD uses the hangcheck timer on Linux platforms.
Extends clusterware to support Oracle-specific requirements and complex resources. Runs server
callout scripts when FAN events occur.
To ensure that each Oracle RAC database instance obtains the block that it needs to satisfy a
query or transaction, Oracle RAC instances use two processes, the Global Cache Service (GCS)
and the Global Enqueue Service (GES). The GCS and GES maintain records of the statuses of
each data file and each cached block using a Global Resource Directory (GRD). The GRD
contents are distributed across all of the active instances.
Voting Disk —
Oracle RAC uses the voting disk to manage cluster membership by way of a health check and
arbitrates cluster ownership among the instances in case of network failures. The voting disk
must reside on shared disk.