ORA-15032 , ORA-15017 , ORA- 15040 , ASM Disk-group not found!!

-

Hello friends, this is something fun which I came across, while trying to troubleshoot an ASM issue.
Usually we know that the diskgroups are an important entity of the ASM infrastructure and working of the database depends a lot upon them.
This particular issue was seen on the standalone ASM database. The ASM diskgroup was nowhere to be found while querying the v$asm_diskgroup and v$asm_disks dynamic tables.

Cause?

There was a change in the hostname of the server, we had to reconfigure the Oracle restart.
Post the changes, we ran the crsctl stat res -t command to check the status of the resources.

--------------------------------------------------------------------------------NAME           TARGET  STATE        SERVER                   STATE_DETAILS   
-----------------------------------------------------------------------------   Local Resources   
-------------------------------------------------------------------------------ora.asm                  ONLINE  ONLINE       testdev03                Started   ora.ons                  OFFLINE OFFLINE      testdev03   
--------------------------------------------------------------------------------Cluster Resources   
-------------------------------------------------------------------------------ora.cssd         
1        ONLINE  ONLINE       testdev03   
ora.diskmon         
1        OFFLINE OFFLINE   
ora.evmd         
1        ONLINE  ONLINE       testdev03

Although the ASM is started, we can enter the asmcmd but the mount-points were not visible and mounting the disk-groups manually fails.

SYS@+ASM> alter diskgroup DATA mount;
alter diskgroup DATA mount*ERROR at line 1:ORA-15032: not all alterations performed ORA-15017: diskgroup "DATA" cannot be mounted
ORA-15040: diskgroup is incomplete


Check the asm_diskstring parameter,
show parameter asm_diskstring. If the output is ORCL:*
So to overcome this issue, we have to change the asm_diskstring parameter.

cd $GRID_HOME/bin
kfod asm_diskstring='/dev/oracleasm/disks/*' disks=all
--------------------------------------------------------------------------------
Disk          Size Path                                    User    Group
================================================================================
  1:    204800 Mb /dev/oracleasm/disks/ASMDISK01          oracle  dba
  2:    204800 Mb /dev/oracleasm/disks/ASMDISK02          oracle  dba
  3:    204800 Mb /dev/oracleasm/disks/ASMDISK03          oracle  dba
  4:    204800 Mb /dev/oracleasm/disks/ASMDISK04          oracle  dba
  5:    204800 Mb /dev/oracleasm/disks/ASMDISK05          oracle  dba
  6:    204800 Mb /dev/oracleasm/disks/ASMDISK06          oracle  dba
  7:    204800 Mb /dev/oracleasm/disks/ASMDISK07          oracle  dba
  8:    204800 Mb /dev/oracleasm/disks/ASMDISK08          oracle  dba
  9:    204800 Mb /dev/oracleasm/disks/ASMDISK09          oracle  dba
--------------------------------------------------------------------------------
ORACLE_SID ORACLE_HOME
================================================================================
      +ASM /u01/app/oracle/product/19.0.0.0/grid_home

Log in to the ASM instance as sysasm and set the asm_diskstring to what it was:

SQL> alter system set asm_diskstring='/dev/oracleasm/disks/*' scope=memory;

System altered.

SQL> select name, state from v$asm_diskgroup;

NAME                           STATE
------------------------------ -----------
DATA                           DISMOUNTED
FRA                            DISMOUNTED

SQL> alter diskgroup DATA mount;

Diskgroup altered.

SQL> alter diskgroup FRA mount;

Diskgroup altered.

SYS@+ASM> select name, state from v$asm_diskgroup;

NAME                           STATE
------------------------------ -----------
DATA                           MOUNTED
FRA                            MOUNTED

This is how the issue got resolved and the disks were visible again.

Comments

Post a Comment

Popular posts from this blog

Register Archive log file manually in standby Database

-
  Some time, the archive logs are not shipping to standby location due to network issue.  There may be  several  archive logs are waiting in standby location for one archive log file. For instance, Archive log sequence # 100 is not shipped to standby location. But other archive logs(sequence#101 to sequence#200) were shipped to standby and it is waiting to ship the sequence# 100.  In this scenario, DBA can copy the archive log file and register manually. Once manually registered, the sequence#101 to sequence#200 will apply automatically on standby database. Step 1 Let us assume, the archive log file devdb12_1_283_801988635.arc is not shipped to standby due to some reason. Copy the archive log file devdb12_1_283_801988635.arc manually from primary to standby archive destination location. Step  2 Run the below command in standby database. ALTER DATABASE REGISTER LOGFILE '/dbArch/oradata/devdb12/ devdb12_1_283_801988635.arc';   Step  3 Verify th...
Read more

Step by Step: How to troubleshoot a slow running query in Oracle

-
This is a day to day task of a DBA. Someone from application team comes to our desk and simply says a query is running slow. We may question him on many things but ultimately a DBA has to tune the query at the end. This is also very popular and known question for the DBA's who are attending interviews. This question is simply asked again and again. I have also been asked this question multiple times. After a pause, interviewer simply asks...so suppose a user comes and reports that his query is running slow, what will be your approach to tune this. There is no absolute or concrete answer to this question because there might be multiple way to tune a slow running query. Everyone can have a different approach. So here is my approach: Very first thing we have to find which type of query is running slow. Whether it is SELECT query of DML statements(insert, update, delete and merge). So first we will see how to tune a SELECT query Step 1 – Find the SQL_ID of the ...
Read more

OCR & OLR in RAC

-
OCR (Oracle Cluster Registry) & OLR (Oracle Local Registry) In this section, I am going to cover the details about OCR (Oracle Cluster Registry) and OLR (Oracle Local Registry). Let's go into the topic!!! OCR (Oracle Cluster Registry) OCR will have all the cluster information. If the OCR is loss, the entire cluster will be affected.  OCR is the central repository which stores the metadata, configuration, status of the clusterware resources.OCR is used to maintain application resources and availability.It also stores configuration information for CRS daemons and clusterware managed applications. Below are the information stored in the OCR. Node membership information ex: which nodes are the part of the cluster Software active version Server pools Status/Configuration for the cluster resources such as RAC databases, listeners, instances and services ASM instance and disk groups CRS application resource profiles such as VIP addresses etc.. Database services characteri...
Read more