ohasd = Oracle High Availability Services Daemon
Link to Oracle Clusterware components
Here is the Oracle 11gR2 clusterware startup sequence:
ohasd -> orarootagent -> ora.cssdmonitor : Monitors CSSD and node health (along with the cssdagent). Try to restart the node if the node is unhealthy.
-> ora.ctssd : Cluster Time Synchronization Services Daemon ->
ora.crsd -> oraagent -> ora.LISTENER.lsnr
-> ora.LISTENER_SCAN.lsnr
-> ora.ons
-> ora.eons
-> ora.asm
-> ora.DB.db
->orarootagent -> ora.nodename.vip
-> ora.net1.network
-> ora.gns.vip
-> ora.gnsd
-> ora.SCANn.vip
-> cssdagent -> ora.cssd : Cluster Synchronization Services
-> oraagent -> ora.mdnsd : Used for DNS lookup
-> ora.evmd
-> ora.evmd
-> ora.asmd
-> ora.gpnpd : Grid Plug and Play = adding a node to the cluster is easier (we need less configuration for the new node)
If a resource is written using blue & bold font => resource owned by root. The other resources are owner by oracle. (all this on UNIX environment)
When a resource is managed by root, we need to run the command
crsctl as root or oracle.
Clusterware Resource Status Check
$ crsctl status resource -t --------------------------------------------------------------------------------NAME TARGET STATE SERVER STATE_DETAILS--------------------------------------------------------------------------------Local Resources--------------------------------------------------------------------------------ora.LISTENER.lsnr ONLINE ONLINE rac1.nitish.com ONLINE ONLINE rac2.nitish.comora.asm OFFLINE OFFLINE rac1.nitish.com OFFLINE OFFLINE rac2.nitish.comora.eons ONLINE ONLINE rac1.nitish.com ONLINE ONLINE rac2.nitish.comora.gsd OFFLINE OFFLINE rac1.nitish.com OFFLINE OFFLINE rac2.nitish.comora.net1.network ONLINE ONLINE rac1.nitish.com ONLINE ONLINE rac2.nitish.comora.ons ONLINE ONLINE rac1.nitish.com ONLINE ONLINE rac2.nitish.com--------------------------------------------------------------------------------Cluster Resources--------------------------------------------------------------------------------ora.LISTENER_SCAN1.lsnr1 ONLINE ONLINE rac1.nitish.comora.LISTENER_SCAN2.lsnr1 ONLINE ONLINE rac2.nitish.comora.LISTENER_SCAN3.lsnr1 ONLINE ONLINE rac2.nitish.comora.oc4j1 OFFLINE OFFLINEora.scan1.vip1 ONLINE ONLINE rac1.nitish.comora.scan2.vip1 ONLINE ONLINE rac2.nitish.comora.scan3.vip1 ONLINE ONLINE rac2.nitish.comora.NITI.db1 ONLINE ONLINE rac1.nitish.com Open2 ONLINE ONLINE rac2.nitish.comora.rac1.nitish.com.vip1 ONLINE ONLINE rac1.nitish.comora.rac2.nitish.com.vip1 ONLINE ONLINE rac2.nitish.com
crsctl start has
-> start all the clusterware services/ resources (including the database server and the listener);
crsctl stop has
-> stop all the clusterware services/ resources (including the database server and the listener);
crsctl check has
-> to check if ohasd is running/ stoppedcrsctl check hasCRS-4638: Oracle High Availability Services is online>> the ohasd daemon is running => the clusterware is (must be) up and running (if no error occur).crsctl check hasCRS-4639: Could not contact Oracle High Availability Services>> the ohasd daemon is NOT running => the clusterware is DOWN (stopped).
crsctl enable has
-> enable Oracle High Availability Services autostart
crsctl disable has
-> disable Oracle High Availability Services autostart
crsctl config has
-> check if Oracle High Availability Services autostart is enabled/ disabled.crsctl config hasCRS-4622: Oracle High Availability Services autostart is enabled.
Nice post....
ReplyDelete