Stops the Oracle Clusterware applications for the database, all or named instances, all or named service names, listeners, or node level application resources. Only the Oracle Clusterware applications that are enabled, starting or running are stopped. Objects running outside of Oracle Clusterware are not stopped.
You should disable an object that you intend to remain stopped after you issue a srvctl stop command. See the srvctl disable command.
Note:
If the object is stopped and is not disabled, then it can restart as the result of another planned operation. The object does not restart because of a failure. Oracle recommends that you disable any object that should remain stopped after you issue a stop command.
When you use the -force parameter to stop dependent applications and the object, then those dependent applications do not restart when the object is later restarted or after the node fails. You must restart the dependent applications, manually, except for services with AUTOMATIC management policy when a database is stopped.
Table A-185 srvctl stop Summary
| Command | Description |
|---|---|
|
Stops Oracle ASM instances |
|
|
Stops the Cluster Verification Utility resource |
|
|
Stops the cluster database |
|
|
Stops a specific disk group on a specified number of nodes |
|
|
Stops the Oracle ACFS volume resource |
|
|
Stops GNS |
|
|
Stops a specific highly available VIP (used for highly available NFS exports) |
|
|
Stops the resources for the specified Oracle home |
|
|
Stops the instance |
|
|
Stops the specified listener or listeners |
|
|
Stops the management database |
|
|
Stops the management listener |
|
|
Stops the node-level applications |
|
|
Stops the OC4J instance |
|
|
Stops Oracle Notification Service |
|
|
Stops all SCAN VIPs |
|
|
Stops all SCAN listeners |
|
|
Stops the service |
|
|
Stops VIP resources |
|
|
Stops a volume device |