Skip to main content

Adding Disk to ASM Disk Group

 Adding a Disk to existing ASM disk group:


Before proceeding with the below steps, capture the ASM current utilization details by using the below query.

SELECT NAME, TOTAL_MB/1024 total_gb, FREE_MB/1024 free_gb, ROUND((1- (FREE_MB / TOTAL_MB))*100, 2)  "percentage used" FROM v$asm_diskgroup order by 4 desc
/

NAME                       TOTAL_GB    FREE_GB       percentage used
------------------------------ ---------- ---------- ---------------
DATA                          8388.75781   146.347656        98.26
INDX                          4144.38281   78.4140625        98.11
OCR                            24.9414063   10.640625          57.34
REDO                         24.9414063   22.578125          9.48
OCRMIRROR            24.9414063   23.9101563        4.13
FRA                            299.429688    291.511719       2.64


Step 1: Check whether any asm operation is running in the background:

SQL> SELECT GROUP_NUMBER, PASS, STATE FROM V$ASM_OPERATION;

no rows selected

Step 2: Check the new disk allocated status , new disk will show as candidate.

set lines 999;
col diskgroup for a15
col diskname for a15
col path for a35
select a.name DiskGroup,b.name DiskName, b.total_mb, (b.total_mb-b.free_mb) Used_MB, b.free_mb,b.path,b.header_status
from v$asm_disk b, v$asm_diskgroup a
where a.group_number (+) =b.group_number
order by b.group_number,b.name;

DISKGROUP  DISKNAME      TOTAL_MB  USED_MB    FREE_MB PATH                                HEADER_STATU
--------------- -------------- ---------- ---------- ---------- ----------------------------------- ------------
                                                               0               0              0                   /dev/rdsk/idx23                     CANDIDATE
DATA            DATA_0000           204760     201268       3492                    /dev/rdsk/data1                     MEMBER
DATA            DATA_0001           102128     100388       1740                    /dev/rdsk/data2                     MEMBER
DATA            DATA_0002           204528     201016       3512                    /dev/rdsk/data3                     MEMBER
DATA            DATA_0003           204528     201024       3504                    /dev/rdsk/data4                     MEMBER
DATA            DATA_0004           204528     201036       3492                    /dev/rdsk/data5                     MEMBER
DATA            DATA_0005           204528     201020       3508                    /dev/rdsk/data6                     MEMBER
DATA            DATA_0006           204528     201032       3496                    /dev/rdsk/data7                     MEMBER
DATA            DATA_0007           204528     201040       3488                    /dev/rdsk/data8                     MEMBER
DATA            DATA_0008           204528     201028       3500                    /dev/rdsk/data9                     MEMBER
DATA            DATA_0009           204528     201016       3512                    /dev/rdsk/data10                   MEMBER

Step 3: Collect the disk path details from the above step in which the header status shows as candidate.

SQL> alter diskgroup INDX add disk '/dev/rdsk/idx23';

Step 4: Check the Rebalance Status

Monitor the rebalance operation to ensure it completes successfully, its completed once the below query returns no values.

SQL> SELECT * FROM V$ASM_OPERATION;

no rows selected

Step 5: Validate the ASM size post adding the disk:

Once this is done again check the asm current utilization details.

SELECT NAME, TOTAL_MB/1024 total_gb, FREE_MB/1024 free_gb, ROUND((1- (FREE_MB / TOTAL_MB))*100, 2)  "percentage used" FROM v$asm_diskgroup order by 4 desc
/


NAME                        TOTAL_GB    FREE_GB percentage used
------------------------------ ---------- ---------- ---------------
DATA                          8388.75781   146.347656         98.26
INDX                          4244.11719   178.136719          95.8
OCR                            24.9414063   10.640625           57.34
REDO                         24.9414063   22.578125           9.48
OCRMIRROR            24.9414063   23.9101563         4.13
FRA                            299.429688    291.242188        2.73



Comments

  1. Thank you for providing such a comprehensive and insightful explanation of adding disk to existing ASM. Your blog post was extremely helpful in resolving production issue.

    ReplyDelete

Post a Comment

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...

πŸš€ DB BOT: Real-Time Oracle & GoldenGate Monitoring in Slack

In today's fast-paced DevOps environment, quick access to database metrics is essential. This blog will walk you through creating a Slack bot that provides real-time monitoring of Oracle databases and Golden Gate replication. With simple slash commands, your team can check tablespace usage, Flash Recovery Area status, and Golden Gate replication health directly in Slack. Project Overview Our "DB Bot" offers these key capabilities: Monitor tablespace usage across multiple Oracle databases Check Flash Recovery Area (FRA) status on multiple databases View GoldenGate process status across different servers List GoldenGate credential stores Monitor replication lag in GoldenGate Prerequisites Node.js v14+ Python 3.6+ Oracle client libraries (instantclient_21_19) Access to Oracle databases and GoldenGate servers A Slack workspace with permissions to add apps   Project Structure oracle-slack-bot...

Oracle Golden Gate Bi-directional Replication Implementation Guide

Oracle GoldenGate (OGG) is a comprehensive software package for real-time data integration and replication in heterogeneous IT environments. Bi-directional replication enables organizations to maintain synchronized data across multiple data centers, providing high availability, disaster recovery, and load distribution capabilities. This detailed guide provides step-by-step instructions for implementing Oracle GoldenGate bi-directional replication between two Oracle databases. Architecture Overview In this setup, we'll configure: TestDC1 : Primary data center with TestDB1 TestDC2 : Secondary data center with TestDB2 Bi-directional sync : Changes flow in both directions with conflict resolution Step 1: Software Installation ⚠️ SERVER EXECUTION: Perform these steps on BOTH TestDC1 and TestDC2 servers Step 1.1: Download and Prepare Software First, create the necessary directory structure and prepare for installation: # Create directory for the software mkdir /data01/ogg_setup cd /d...