Managing the ASM Instance in Oracle Clusterware srvctl start asm and srvctl stop asm Explained

Demystifying Start/Stop ASM with srvctl in Oracle Database

SQL Code

Start ASM

1srvctl start asm -n <node name>

Stop ASM

1srvctl stop asm -n <node name>

Sample Oracle Output:

2no rows selected

Description of the Oracle Database SQL code:

Demystifying Start/Stop ASM with srvctl in Oracle Database

These commands, specifically srvctl start asm and srvctl stop asm, play a crucial role in managing the Oracle Automatic Storage Management (ASM) instance within your Oracle Clusterware environment. Let's dive into their purpose, breakdown, and key points:


  • srvctl start asm: Initiates the ASM instance on the specified node(s), enabling it to manage disk groups and provide storage services for Oracle databases.
  • srvctl stop asm: Gracefully terminates the ASM instance on the specified node(s), making its associated disk groups unavailable to connected databases.


  • srvctl: The Service Control utility, a command-line tool integral to Oracle Clusterware, facilitates managing various aspects like starting/stopping services, checking node status, and allocating resources.
  • start asm / stop asm: These specific actions target the ASM instance, which handles storage management for Oracle databases within a clustered environment.
  • -n <node name>: Specifies the node(s) where you want to start or stop the ASM instance. You can list multiple nodes separated by commas for simultaneous execution.

Key Points:

  • Impact: These commands significantly impact disk group accessibility and database operations. Starting ASM makes associated disk groups available, while stopping it renders them inaccessible.
  • Node-level control: You manage the ASM instance on individual nodes, allowing flexibility in managing storage across your cluster.
  • Clusterware context: These commands are applicable within an Oracle Clusterware environment, where multiple nodes collectively provide high availability and redundancy for databases.

Additional Insights and Explanations:

  • Permissions: Executing these commands requires appropriate privileges, such as CLUSTER_OPERATIONS or CREATE RESOURCE.
  • Considerations: Carefully assess the potential consequences before using these commands, as they can affect database availability and performance.
  • Alternative options: While these commands manage the ASM instance itself, the srvctl start instance and srvctl stop instance commands control individual database instances within your cluster.
  • Best practices: Consult Oracle documentation and experienced database administrators for comprehensive guidance and potential troubleshooting scenarios.

Posts in this series