Skip to main content

Mastering Oracle RAC with CRSCTL commands

Mastering Oracle Clusterware Administration: Essential Commands & Best Practices

Oracle Clusterware is a key component for managing cluster environments, ensuring high availability and resource management for Oracle databases. Below are essential commands for managing Oracle Clusterware effectively.

What is crsctl?

crsctl (Cluster Ready Services Control) is a command-line utility provided by Oracle to manage Oracle Clusterware. It allows administrators to start, stop, check, and configure various aspects of cluster services. With crsctl, DBAs can control cluster resources, manage voting disks, check the status of Oracle High Availability Services, and ensure the proper functioning of Oracle RAC environments.


Starting and Stopping Oracle Clusterware

On Local Node

  • Stop Clusterware:

    crsctl stop cluster
  • Start Clusterware:

    crsctl start cluster

On RAC Standalone/Oracle Restart

  • Stop Cluster:

    crsctl stop has
  • Start Cluster:

    crsctl start has

On All Nodes or All Hub Nodes

  • Start Clusterware:

    crsctl start cluster

Enabling or Disabling Automatic Startup

  • Enable automatic startup:

    crsctl enable crsctl
  • Disable automatic startup:

    crsctl disable crsctl

Checking Clusterware Status

  • Check CRS status on a local node:

    crsctl check crsctl
  • View Oracle High Availability Stack:

    crsctl stat res -init -t
  • Query Cluster Extended Status:

    crsctl get cluster extended
  • Query Cluster Sites:

    crsctl query cluster site -all
  • Confirm CTSSD is active after installation:

    crsctl check ctss

Managing Cluster Nodes

  • Delete a node from the cluster:

    crsctl delete node -n hostname

Configuring Oracle High Availability Services

  • Display automatic startup configuration:

    crsctl config crs

Checking Cluster Status Across Nodes

  • Check cluster status from all nodes:

    crsctl check cluster -all

Determining Storage Locations

  • Determine the location of the Voting Disk:

    crsctl query css votedisk
  • Determine the location of the Oracle Cluster Registry (OCR):

    ocrcheck -config

Checking Clusterware Version

  • Verify the currently running version:

    crsctl query crs activeversion
  • Check the software version on a single node:

    crsctl query crs softwareversion [hostname]

Stopping and Starting Clusterware Across Nodes

  • Stop Clusterware on all nodes (as root):

    crsctl stop cluster -all
  • Start Clusterware stack on one node in exclusive mode:

    crsctl start crs -excl -nocrs

Managing Voting Disks

  • Add a Voting Disk to non-ASM storage:

    crsctl add css votedisk <path_to_new_voting_disk>
  • Delete a Voting Disk from non-ASM storage:

    crsctl delete css votedisk <path_to_old_voting_disk>
  • Move a Voting Disk to an ASM Disk Group:

    crsctl replace votedisk +asm_disk_group
  • Migrate Voting Disks between ASM and non-ASM storage:

    crsctl replace votedisk {+asm_disk_group | path_to_voting_disk}

Monitoring and Logging

  • Monitor Clusterware-managed resource utility:

    crsctl query calog
  • Query maximum space allocated to cluster resource activity logs:

    crsctl get calog maxsize


By using these commands, Oracle Database Administrators can effectively manage and monitor Oracle Clusterware environments, ensuring high availability and efficient resource management.

Comments

Popular posts from this blog

🚀 Automating Oracle Database Patching with Ansible: A Complete Guide

Oracle database patching has long been the bane of DBAs everywhere. It's a critical task that requires precision, expertise, and often results in extended maintenance windows. What if I told you that you could automate this entire process, reducing both risk and downtime while ensuring consistency across your Oracle estate? 💡 In this comprehensive guide, I'll walk you through a production-ready Ansible playbook that completely automates Oracle patch application using OPatch. Whether you're managing a single Oracle instance or hundreds of databases across your enterprise, this solution will transform your patch management strategy! 🎯 🔥 The Challenge: Why Oracle Patching is Complex Before diving into the solution, let's understand why Oracle patching is so challenging: 🔗 Multiple dependencies : OPatch versions, Oracle Home configurations, running processes ⚠️ Risk of corruption : Incorrect patch application can render databases unusable ⏰ Downtime requirements : Da...

Oracle RAC Switchover & Switchback: Step-by-Step Guide

 Ensuring business continuity requires regular Disaster Recovery (DR) drills. This guide covers the Switchover and Switchback process between Primary (DC) and Standby (DR) databases . Pre-checks Before Performing Switchover Before starting the activity, ensure there are no active sessions in the database. If any are found, share the session details with the application team, get their confirmation, and terminate the sessions. Primary Database Name: PRIMARY Standby Database Name: STANDBY  Identify Active Sessions set lines 999 pages 999 col machine for a30 col username for a30 col program for a30 compute sum of count on report break on report select inst_id,username,osuser,machine,program,status,count(1) "count" from gv$session where inst_id=1 and program like 'JDBC%' group by inst_id,username,osuser,machine,program,status order by 1,2; select inst_id,username,osuser,machine,program,status,count(1) "count" from gv$session where inst_id=2 and program lik...

Mastering Oracle RAC with SRVCTL Commands

Oracle Real Application Clusters (RAC) provide high availability, scalability, and manageability for databases. One of the most powerful tools for managing RAC databases is srvctl , a command-line utility that allows administrators to control various database services. This blog explores essential srvctl commands to help you efficiently manage Oracle RAC environments. 1. Checking Database Configuration and Status  List all available databases on the host:                  srvctl config database   Check the status of a specific database and its instances:                    srvctl status database -d <database_name>   Retrieve detailed status information about a database, including its instances and states:                    srvctl status database -d <database_name> -v 2. Stopping and Starting Databases   ...