Sunday, January 23, 2022
    HomeOracle TroubleshootingASM Disk creation issue

    ASM Disk creation issue

    Problem creating ASM disk with ASMLib

    There are lots of general issues happening or encountering when we are trying to create new ASM disk. The following case may occur when trying to create an ASM disk with Oracle ASMLib.

    I am providing accurate solution to get rid of this issue. I was working with a client of UK that time they was encountering this issue in their Oracle database server. They tried to get rid of this issue but got unsuccessful. Due to they opened ticket with our Dbametrix. We were providing remote Oracle DBA support them. My team tried and searched so many things on web and tested most of solutions got from blogs and workarounds from Oracle forums and blogs.

    - Advertisement -

    After that we got workaround from Oracle support note and we deployed same to our client. We got success to create new ASM disk using same name and able to map it with existing Oracle ASM instance. I am describing same solution here for troubleshooting this kind of mysterious issue of ASM.

    [[email protected] asmserver101 /] # / usr / sbin / oracleasm createdisk ASMDISK201 / dev /mapper /ASMDISK201

    Device “/dev /mapper /ASMDISK201” is already labeled for ASM disk “ASMDISK201”

    [[email protected] asmserver101/] # multipath -ll

    - Advertisement -

    ASMDISK201 (321260203626233005b20a4sf5ce266) dm-8 DGC, VRAID

    size = 4.0G features = ‘1 queue_if_no_path’ hwhandler = ‘1 emc’ wp = rw

    | = ‘service-time 0’ prio = 6 status = active

    | | – 0: 0: 3: 1 sdi 8:32 active ready running

    | `- 3: 0: 3: 1 sde 8:96 active ready running`

    – + – policy = ‘service-time 0’ prio = 1 status = enabled

    | – 0: 0: 0: 1 sdc 8:128 active ready running

    `- 3: 0: 0: 1 sdg 8:64 active ready running

    Probably the problem is that the disk is already “marked” as ASM. It might happen because it was already element of an installation or for some reason it was eliminated from ASM and resubmitted. In any of the cases, to solve the problem, simply as the “root” user we execute the following command that steps on the header on the disk, leaving it free of mark:

    dd if = /dev / zero of = / dev / mapper / ASMDISK201 bs = 1024 count = 100

    Then we attempt to generate the disk again, and we do it without difficulties:

    [[email protected] asmserver101/] # /usr/sbin/oracleasm createdisk ASMDISK201 / dev/mapper/ASMDISK201

    Writing disk header: done
    Instantiating disk: done

    [[email protected] asmserver101/] # /usr /sbin/oracleasm listdisks


    [[email protected] asmserver101/] # / usr / sbin / oracleasm querydisk /dev/mapper/ASMDISK201

    Device “/dev/mapper /ASMDISK201” is marked an ASM disk with the label “ASMDISK201”

    Using above trick, you can troubleshoot this mysterious automatic storage management disk issue in Oracle ASM instance.

    When you want to make a strong Oracle DBA career then you should be aware of database services and other database technology. Without having knowledge of Oracle internals, Oracle performance tuning, and skill of Oracle database troubleshooting you can’t be an Oracle DBA expert. This expert DBA Team club blog always provides you latest technology news and database news to keep yourself up to date. You should need to be aware of Cloud database technology like DBaaS. These all Oracle DBA tips are available in a single unique resource at our orageek. Meanwhile, we are also providing some sql tutorials for Oracle DBA. This is the part of Dbametrix Group and you would enjoy more advanced topics from our partner resource.

    Consider Reading to these articles:

    - Advertisement -


    1. I experienced with same kind of ASM disk issue. After recreating ASM disk, it was get resolved. Thanks for sharing. I am very lazy to write and share these things. Always read from some blog.

    Comments are closed.

    - Advertisment -

    Most Popular

    Recent Comments