Professional Documents
Culture Documents
i).ClusterReadyServices(CRS)
crsd.bin The above process is responsible for start, stop, monitor and failover of resource. It maintains OCR and also
restarts the resources when the failure occurs.
This is applicable for RAC systems. For Oracle Restart and ASM ohasd is used.
ii).ClusterSynchronizationService(CSS)
cssdmonitor Monitors node hangs (via oprocd functionality) and monitors OCCSD process hangs (via oclsomon
functionality) and monitors vendor clusterware(via vmon functionality).This is the multi-threaded process that runs with
elevated priority.
Startup sequence: INIT init.ohasd ohasd ohasd.bin cssdmonitor
cssdagent Spawned by OHASD process. Previously(10g) oprocd, responsible for I/O fencing. Killing this process
would cause node reboot. Stops, start checks the status of occsd.bin daemon
Startup sequence: INIT init.ohasd ohasd ohasd.bin cssdagent
occsd.bin Manages cluster node membership runs as oragrid user. Failure of this process results in node restart.
Startup sequence: INIT init.ohasd ohasd ohasd.bin cssdagent ocssd ocssd.bin
iii)EventManagement(EVM)
evmd.bin Distributes and communicates some cluster events to all of the cluster members so that they are aware of the
cluster changes.
evmlogger.bin Started by evmd.bin reads the configuration files and determines what events to subscribe to from
EVMD and it runs user defined actions for those events.
iv).OracleRootAgent
orarootagent.bin A specialized oraagent process that helps crsd manages resources owned by root, such as the
network, and the Grid virtual IP address.
The above 2 process are actually threads which looks like processes. This is a Linux specific
v).ClusterTimeSynchronizationService(CTSS)
vi).OracleAgent
oraagent.bin Extends clusterware to support Oracle-specific requirements and complex resources. This process runs
server callout scripts when FAN events occur. This process was known as RACG in Oracle Clusterware 11g Release 1
(11.1).
i).ClusterLoggerService
ologgerd Receives information from all the nodes in the cluster and persists in a CHM repository-based database. This
service runs on only two nodes in a cluster
ii).SystemMonitorService(osysmond)
osysmond The monitoring and operating system metric collection service that sends the data to the cluster logger
service. This service runs on every node in a cluster
iii).GridPlugandPlay(GPNPD):
gpnpd.bin Provides access to the Grid Plug and Play profile, and coordinates updates to the profile among the nodes of
the cluster to ensure that all of the nodes have the most recent profile.
iv).GridInterprocessCommunication(GIPC):
v).MulticastDomainNameService(mDNS):
mdnsd.bin Used by Grid Plug and Play to locate profiles in the cluster, as well as by GNS to perform name resolution.
The mDNS process is a background process on Linux and UNIX and on Windows.
vi).OracleGridNamingService(GNS)
OCR: It created at the time of Grid Installation. Its store information to manage Oracle cluster-ware and its component
such as RAC database, listener, VIP, Scan IP & Services.
Minimum 1 and maximum 5 copy of OCR is possible.
Voting Disk: It manage information about node membership. Each voting disk must be accessible by all nodes in the
cluster. If any node is not passing heat-beat across other note or voting disk, then that node will be evicted by Voting disk.
Minimum 1 and maximum 15 copy of voting disk is possible.
New Facts:
We can store OCR and Voting disk on ASM or certified cluster file system.
We can dynamically add or replace voting disk & OCR.
Backup of Voting disk using dd command not supported.
Voting disk and OCR can be keep in same disk-group or different disk-group
Voting disk and OCR automatic backup kept together in a single file.
Automatic backup of Voting disk and OCR happen after every four hours, end of the day, end of the week
You must have root or sudo privilege account to manage it.