This content has been marked as final. Show 3 replies
To understand the basic difference b/w all three commands, first you need to understand the daemon process architecture:
There are four levels of daemons are there from 11.2 onward.
Level-1 : OHASD'S Spawn_
Here OHASD(Super Daemon process) will spawn itself and it will start :
a) CSSDAGENT, b) CSSDMONITOR, c) ORAROOTAGENT and d) ORAAGENT
Level-2: OHASD cssdagent, cssdmonitor, orarootagent and oraagent spawn_
Here cssdagent, cssdmonitor, orarootagent and oraagent, they all will start:
a) CSSD, b) CRSD, c) CTSSD, d) DISKMON, e) GIPCD, f) GPNPD, g) EVMD, h) MDNSD etc.
Level-3: CRSD spawns:_
In this level CRSD will start again:
a) ORAROOTAGENT and b) ORAAGENT
Level-4: CRSD orarootagent and oraagent SPAWNS:_
Both orarootagent and oraagent both will start all the resources like ASM, DB, LISTENER, VIPs etc.
Now Answer for your question:
*# CRSCTL STOP CLUSTER:*
This command will stop all the resources being managed by CRSD's Oragent & Orarootagent.
*# CRSCTL STOP CRS:*
This command will stop entire gridInfra i.e all daemons.
*# CRSCTL STOP HAS:*
This command is similar like CRSCTL STOP CRS but better to use this command in standalone server having GridInfra.
Edited by: Ashish Shukla on May 20, 2013 3:39 PM