Skip to main content

ASM Disks Migration from Old storage to New storage on RAC

 Check Number of Disk Groups

SQL> select name,path, total_mb, state, mount_status, header_status from v$asm_disk;


NAME                      PATH                            TOTAL_MB   STATE   MOUNT_STATUS HEADER_STATUS

--------------   ------------------------------      ----------     --------      --------------         ------------

DATA_0000      /dev/oracleasm/disks/DATA      225264    NORMAL      CACHED                MEMBER

FRA_0000        /dev/oracleasm/disks/FRA          92160    NORMAL      CACHED                MEMBER

CRS_0000        /dev/oracleasm/disks/CRS          92160    NORMAL      CACHED               MEMBER

1. Backup the database using RMAN and validate the backups.

2. Check Old Disk's added on what sd* just to verify

prodmachine22:/dev/oracleasm/disks # ll
total 0
brw-rw---- 1 grid asmadmin 8, 37 Jan 14 05:00 CRS
brw-rw---- 1 grid asmadmin 8, 39 Jan 14 05:00 DATA
brw-rw---- 1 grid asmadmin 8, 38 Jan 14 05:00 FRA


prodmachine22:/dev/oracleasm/disks # ls -lha /dev | grep -w "8,.*37"
brw-rw----   1 root disk      8,  37 Jan 13 14:31 sdc5

prodmachine22:/dev/oracleasm/disks # ls -lha /dev | grep -w "8,.*39"
brw-rw----   1 root disk      8,  39 Jan 13 14:31 sdc7

prodmachine22:/dev/oracleasm/disks # ls -lha /dev | grep -w "8,.*38"
brw-rw----   1 root disk      8,  38 Jan 13 14:31 sdc6

Now that all disks are confirmed on sdc5,6 and 7.

3. Add same size New Lun (storage) and verify with lsblk

# lsblk

Old Disks
├─sdc1             8:33   0    1K  0 part
├─sdc5             8:37   0   90G  0 part
├─sdc6             8:38   0   90G  0 part
└─sdc7             8:39   0  220G  0 part

New Disks added
sdd                8:48   0  400G  0 disk
├─sdd1             8:49   0    1K  0 part
├─sdd5             8:53   0   90G  0 part
├─sdd6             8:54   0   90G  0 part
└─sdd7             8:55   0  220G  0 part

4. We will create new Disks mentioned below

sdd5 for CRS
sdd6 for FRA
sdd7 for DATA

oracleasm createdisk CRSNEW /dev/sdd5
oracleasm createdisk FRANEW /dev/sdd6
oracleasm createdisk DATANEW /dev/sdd7


prodmachine22:# oracleasm createdisk CRSNEW /dev/sdd5
Writing disk header: done
Instantiating disk: done

prodmachine22:# oracleasm createdisk FRANEW /dev/sdd6
Writing disk header: done
Instantiating disk: done

prodmachine22:# oracleasm createdisk DATANEW /dev/sdd7
Writing disk header: done
Instantiating disk: done

prodmachine22:/dev/oracleasm/disks # ll
total 0
brw-rw---- 1 grid asmadmin 8, 37 Jan 14 05:21 CRS
brw-rw---- 1 grid asmadmin 8, 53 Jan 14 05:20 CRSNEW
brw-rw---- 1 grid asmadmin 8, 39 Jan 14 05:21 DATA
brw-rw---- 1 grid asmadmin 8, 55 Jan 14 05:21 DATANEW
brw-rw---- 1 grid asmadmin 8, 38 Jan 14 05:21 FRA
brw-rw---- 1 grid asmadmin 8, 54 Jan 14 05:20 FRANEW

5. On other nodes Scan for new added disks

prodmachine23:~ # oracleasm listdisks
CRS
DATA
FRA

prodmachine23:~ # oracleasm scandisks
Reloading disk partitions: done
Cleaning any stale ASM disks...
Scanning system for ASM disks...
Instantiating disk "CRSNEW"
Instantiating disk "FRANEW"
Instantiating disk "DATANEW"

prodmachine23:~ # oracleasm listdisks
CRS
CRSNEW
DATA
DATANEW
FRA
FRANEW

6. Add new disks to the existing disk group.

Connect to grid user and connect sqlplus as /as sysasm


SQL> 
set pages 300 lines 120
col PATH for a30
select DISK_NUMBER,MOUNT_STATUS,HEADER_STATUS,MODE_STATUS,STATE,
PATH FROM V$ASM_DISK;

DISK_NUMBER MOUNT_S HEADER_STATU MODE_ST STATE    PATH
----------- ------- ------------ ------- -------- ------------------------------
          0 CLOSED  PROVISIONED  ONLINE  NORMAL   /dev/oracleasm/disks/CRSNEW
          1 CLOSED  PROVISIONED  ONLINE  NORMAL   /dev/oracleasm/disks/DATANEW
          2 CLOSED  PROVISIONED  ONLINE  NORMAL   /dev/oracleasm/disks/FRANEW
          0 CACHED  MEMBER       ONLINE  NORMAL   /dev/oracleasm/disks/DATA
          0 CACHED  MEMBER       ONLINE  NORMAL   /dev/oracleasm/disks/FRA
          0 CACHED  MEMBER       ONLINE  NORMAL   /dev/oracleasm/disks/CRS

6 rows selected.


SQL> 
select name, total_mb, state, type from v$asm_diskgroup;

NAME                             TOTAL_MB STATE       TYPE
------------------------------ ---------- ----------- ------
CRS                                 92160 MOUNTED     EXTERN
DATA                               225264 MOUNTED     EXTERN
FRA                                 92160 MOUNTED     EXTERN




Alter the diskgroup to add new disks and wait until the rebalace operation is completed

SQL> alter diskgroup DATA add disk '/dev/oracleasm/disks/DATANEW' rebalance power 11;

Diskgroup altered.

Wait for rebalance to complete by checking with below queries:

select * from v$asm_operation;
select * from gv$asm_operation;

Wait until output comes to

SQL> 
no rows selected

SQL> alter diskgroup FRA add disk '/dev/oracleasm/disks/FRANEW' rebalance power 11;

Diskgroup altered.

Keep checking the rebalance manually and proceed ahead.


SQL> alter diskgroup CRS add disk '/dev/oracleasm/disks/CRSNEW' rebalance power 11;

Diskgroup altered.

Keep checking rebalance manually and proceed ahead.



7. Verify the newly added disks:

SQL> 
select name, total_mb, state, type from v$asm_diskgroup;

NAME                             TOTAL_MB STATE       TYPE
------------------------------ ---------- ----------- ------
CRS                                184320 MOUNTED     EXTERN
DATA                               450540 MOUNTED     EXTERN
FRA                                184320 MOUNTED     EXTERN

Size of disks increased after disk addition.


SQL>
select name,path, total_mb, state, mount_status, header_status from v$asm_disk;

NAME       PATH                             TOTAL_MB STATE    MOUNT_STATUS HEADER_STATUS
----------------------------------------- ---------- -------- -------       ------------
DATA_0000  /dev/oracleasm/disks/DATA          225264 NORMAL   CACHED        MEMBER
FRA_0000   /dev/oracleasm/disks/FRA            92160 NORMAL   CACHED        MEMBER
CRS_0000   /dev/oracleasm/disks/CRS            92160 NORMAL   CACHED        MEMBER
DATA_0001  /dev/oracleasm/disks/DATANEW       225276 NORMAL   CACHED        MEMBER
FRA_0001   /dev/oracleasm/disks/FRANEW         92160 NORMAL   CACHED        MEMBER
CRS_0001   /dev/oracleasm/disks/CRSNEW         92160 NORMAL   CACHED        MEMBER


8. Remove the old disks from the diskgroups

SQL>
alter diskgroup DATA drop disk 'DATA_0000' rebalance power 11;

Diskgroup altered.

Wait for rebalance to complete, then proceed.


SQL> 
alter diskgroup FRA drop disk 'FRA_0000' rebalance power 11;

Diskgroup altered.

Wait for rebalance to complete, then proceed.

SQL>
alter diskgroup CRS drop disk 'CRS_0000' rebalance power 11;

Diskgroup altered.

Then wait until the rebalance operation is completed.

Rebalance Check query:

select * from v$asm_operation;
select * from gv$asm_operation;

Output:
SQL> 
select * from gv$asm_operation;

GROUP_NUMBER OPERA PASS      STAT      POWER     ACTUAL      SOFAR   EST_WORK   EST_RATE EST_MINUTES ERROR_CODE   CON_ID
------------ ----- --------- ---- ---------- ---------- ---------- ---------- ---------- ----------- ------------ -------
           3 REBAL COMPACT   WAIT         11         11          0          0          0           0              0
           3 REBAL REBALANCE RUN          11         11        382        474      29802           0              0
           3 REBAL REBUILD   DONE         11         11          0          0          0           0              0



SQL> set linesize 200
set pagesize 200
col path for a30
select name,path, total_mb, state, mount_status, header_status from v$asm_disk;

NAME                           PATH                             TOTAL_MB STATE    MOUNT_S HEADER_STATU
------------------------------ ------------------------------ ---------- -------- ------- ------------
                               /dev/oracleasm/disks/DATA               0 NORMAL   CLOSED  FORMER
                               /dev/oracleasm/disks/FRA                0 NORMAL   CLOSED  FORMER
                               /dev/oracleasm/disks/CRS                0 NORMAL   CLOSED  FORMER
DATA_0001                      /dev/oracleasm/disks/DATANEW       225276 NORMAL   CACHED  MEMBER
FRA_0001                       /dev/oracleasm/disks/FRANEW         92160 NORMAL   CACHED  MEMBER
CRS_0001                       /dev/oracleasm/disks/CRSNEW         92160 NORMAL   CACHED  MEMBER

6 rows selected.

9. Now delete the disk from ASM and release the storage

List the disks

prodmachine22:~ # oracleasm listdisks

CRS

CRSNEW

DATA

DATANEW

FRA

FRANEW

Delete the disk from ASM

oracleasm deletedisk DATA

oracleasm deletedisk FRA

oracleasm deletedisk CRS

output:

prodmachine22:~ # oracleasm deletedisk DATA

Clearing disk header: done

Dropping disk: done

prodmachine22:~ # oracleasm deletedisk FRA

Clearing disk header: done

Dropping disk: done

prodmachine22:~ # oracleasm deletedisk CRS

Clearing disk header: done

Dropping disk: done


Validate the Disks

prodmachine22:~ # oracleasm listdisks

CRSNEW

DATANEW

FRANEW


Scan Disks on 2nd node.

prodmachine23:~ # oracleasm listdisks

CRS

CRSNEW

DATA

DATANEW

FRA

FRANEW


prodmachine23:~ # oracleasm scandisks

Reloading disk partitions: done

Cleaning any stale ASM disks...

Cleaning disk "CRS"

Cleaning disk "DATA"

Cleaning disk "FRA"

Scanning system for ASM disks...

prodmachine23:~ # oracleasm listdisks

CRSNEW

DATANEW

FRANEW

We have successfully migrated ASM disks from old storage to new on RAC.




Labels:

Comments

Post a Comment

Popular posts from this blog

Upgrade Oracle Database 12c to 19c by DBUA Method

  Introduction Upgrade Oracle Database is a crucial step to ensure you're benefiting from the latest features, performance enhancements, and security updates. In this guide, we'll walk you through the process of upgrading your Oracle Database 12c to the latest version, 19c . Follow these steps to ensure a smooth and successful upgrade Environment Hostname : prod.infoinflux.com Database Name : PROD DB VERSION : 12.2.0.1.0 ORACLE_BASE : /u01/app/oracle DB Home Path : /u01/app/oracle/product/12.2.0.1/db_1 Datafile Location : /u01/app/oracle/oradata/PROD Target DB VERSION : 19.0.0.0 Target DB Path : /u01/app/oracle/product/19c/db_1 Upgrade Method : Database Upgrade Assistant Steps For upgrade using Database Upgrade Assistant (DBUA): Take Latest Database backup Make Directory for 19c Home Download and Unzip Software to 19c Home Directory Install 19c Binary or Software Create Pre and Post Upgrade Scripts Run Pre-Upgrade Script Pre-Upgra...
Post a Comment
Read more

Install Oracle Linux 6 or any version in VM Virtual Box

 1. Download & Install Oracle Linux from the Link: https://www.oracle.com/in/virtualization/technologies/vm/downloads/virtualbox-downloads.html 2. Download any ISO file from the link: https://yum.oracle.com/oracle-linux-isos.html I have downloaded 6.8 version iso 3. Let’s create the Linux machine using the same ISO. Click on New for creating new virtual machine. 4. Now Put Name and create a folder naming PROD or any other name as per your requirement. In my case my system D drive has enough of space, so I created a folder naming PROD and download the ISO image in same drive. I have Selected ISO image which I downloaded. Note: Make sure you select Skip Unattended Installation. Click Next. 5. I have 16 GB ram in my system so I am giving 4 GB(4096 MB), you can gives as per your system resources. Click Next 6. Now give Hard disk size you want to assign to your machine. Select pre-allocate Full Size. Click Next. 7. It wi...
Post a Comment
Read more

Create Local Yum Repository In Linux From ISO Image

 A local YUM repository in Linux is a collection of RPM (Red Hat Package Manager) packages stored on a local server or file system. YUM (Yellowdog Updater, Modified) is a package management tool commonly used in Red Hat-based Linux distributions like CentOS, Fedora, and Red Hat Enterprise Linux. It simplifies the process of installing, updating, and managing software packages on a Linux system. In this we'll try to create one. Steps to follow: Mount the iso image in virtual machine. Install vsftpd rpm from the iso Packages. Copy the packages from iso to /var/ftp/pub/Packages/ Install createrepo .rpm  from packages and Create repo in location /var/ftp/pub/ Create new repo file in location /etc/yum.repos.d/{any_name.repo} and add entry Check and start the vsftpd and Clean & update the yum. 1. Mount the iso image in virtual machine. In the virtual machine select iso image file option in devices. It will be mounted and you can see the ico...
Post a Comment
Read more

Install Oracle Database 12.2(12c) on Linux

  Introduction Installing Oracle Database 12.2 on Linux system might seem daunting at first, but with the right guidance, it can be a smooth process. In this guide, we'll take you through the step-by-step procedure to install Oracle Database on a Linux environment. By the end of this tutorial, you'll have a functional Oracle Database instance up and running. Steps for Installation: 1. Prerequisites Automatic Setup 2. Prerequisites Manual Setup 3. Install Oracle Database Binary (Software only) 4. Create Database by DBCA 1. Prerequisites Automatic Setup To perform all your prerequisite setup automatically, issue the following command or you can proceed with manual setup explained in 2nd point. [ root @ prod ] # yum install oracle - database - server - 12cR2 - preinstall - y 2. Prerequisites Manual Setup a) Download and Unzip the oracle 12.2 Setup Download or copy the oracle setup file to any location as per your requirement. In...
Post a Comment
Read more

Primary & Standby Database SYNC Check in Oracle Database

 In Oracle Data Guard , you can check whether the standby database is in sync with the primary database by monitoring the apply lag. The apply lag represents the time delay between when a redo log is generated on the primary database and when it is applied on the standby database. A zero or low apply lag indicates that the standby is relatively up-to-date with the primary, while a high apply lag suggests a potential synchronization delay. Here are some methods to check whether the standby database is in sync with the primary: 1. Data Guard Broker If you are using the Data Guard Broker, you can use the DGMGRL command-line interface or Enterprise Manager (Grid Control) to check the status of the Data Guard configuration and monitor the apply lag. For example, using DGMGRL: DGMGRL> SHOW DATABASE 'standby_database_name' APPLY_LAG; DGMGRL > SHOW DATABASE 'standby_database_name' APPLY_LAG ; 2. V$DATAGUARD_STATS View On the primary datab...
Post a Comment
Read more

ORA-12012: error on auto execute of job SYS.ORA$AT_OS_OPT_SY_**

  Introduction ORA-12012 error is related to Oracle Database and is part of the Oracle Job Scheduler (DBMS_SCHEDULER) . It usually occurs when an automatic task or job execution encounters an issue. The error message you're seeing, " ORA$AT_OS_OPT_SY_<number> ," is specific to the job causing the problem. During the 12c database creation process, you can see ORA-12012 error in the alert log file when the “ SYS.ORA$AT_OS_OPT_SY_ ” auto job runs. To fix the error, it is necessary to drop the job and recreate it. Errors will be as follows. Errors in file /u01/app/oracle/diag/rdbms/prod/PROD/trace/PROD_j000_14524.trc: ORA-12012: error on auto execute of job "SYS"."ORA$AT_OS_OPT_SY_767" ORA-20001: Statistics Advisor: Invalid task name for the current user ORA-06512: at "SYS.DBMS_STATS", line 47207 ORA-06512: at "SYS.DBMS_STATS_ADVISOR", line 882 ORA-06512: at "SYS.DBMS_STATS_INTERNAL", line 20059 ORA-065...
Post a Comment
Read more

Install Oracle 19c Database on Linux

  Introduction Installing Oracle Database 19c on a Linux system might sound complex, but with a well-structured approach, it can be a smooth process. In this guide, we'll break down the installation steps into simple and easy-to-follow instructions, ensuring you set up or install Oracle 19c successfully on your Linux machine. Steps for Installation: 1. Download 19c Software & Copy it to Location 2. Prerequisites Automatic Setup 3. Prerequisites Manual Setup 4. Install 19c Oracle Database Binary (Software only) 5. Create Database by DBCA 1. Download 19c Software & Copy it to Location a) Download 19c Software on local system: Click here b) Transfer or copy Setup file using WinSCP or Mobaxterm on Linux Machine at any location as preferred. In my case I have copied to /u01 mount. c) Give chmod 775 permission to the setup file. [root@prod u01]# ls 19C_DB.zip [root@prod u01]# chmod 775 19C_DB.zip [ root @ prod u01 ]# ls 19 C_D...
Post a Comment
Read more

RAC Database Shutdown Procedure

  Introduction When it comes to managing an Oracle Real Application Clusters (RAC) database, proper shutdown procedures are crucial to maintain data integrity and prevent potential issues. In this short blog post, we'll guide you through the step-by-step process of shutting down an Oracle RAC DB in sequence using commands, ensuring a smooth and safe shutdown. How to Shutdown Oracle Real Application Clusters Database ? Shutdown Oracle Listener. Shutdown RAC Database Instances on all nodes. Shutdown ASM instances from all nodes. Shutdown Node applications on all nodes. Shut down Oracle Clusterware / CRS. 1. Shutdown Oracle Listener ## To stop listener from all nodes ## [ grid @ node1 ~ ] $ srvctl stop listener ## To Check Status of listener ## [ grid @ node1 ~ ] $ srvctl status listener Listener LISTENER is enabled Listener LISTENER is not running on node ( s ): node1 , node2 ## OTHER COMMANDS ## ## To...
Post a Comment
Read more

RMAN Backup using ShellScript

 In a real time, we will not take Oracle database backup manually everyday. Some of the tasks can be automated like RMAN backups. In this post, we will see how to automate RMAN backup using shellscript and I personally use shellscript for import/export, rman backup and for monitoring alerts. • Create Backup directory • Create RMAN backup script file .sh • Schedule Backup Under Crontab # Example of job definition: # .---------------- minute (0 - 59) # | .------------- hour (0 - 23) # | | .---------- day of month (1 - 31) # | | | .------- month (1 - 12) OR jan,feb,mar,apr ... # | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat # | | | | | # * * * * * user-name command to be executed # Example of job definition: # . ---------------- minute ( 0 - 59 ) # | . ------------- hour ( 0 - 23 ) # | | . ---------- day of month ( 1 - 31 ) # | | | . ------- month ( 1 - 12 ) OR jan , feb , mar , apr .....
Post a Comment
Read more