Oracleasm disks not listed in v$asm_disk

Recently I’ve seen a strange issue with oracleasm disks. Disks were listed in oracleasm but were missing from v$asm_disk view. It was a RAC environment & this was happening only on one node.

node-2:~ # oracleasm listdisks
DK65_1
DK65_10
DK65_11
........ 

node-2:~ # su - ora11gr1

SQL> select name, state, header_status, path,total_mb, free_mb from v$asm_disk
/
no rows selected

But on the first node everything was working as expected.

Now one of the team member told me that there was a RAC configuration issue, and few temporary files were removed. Metalink Note ID 359266.1 was really handy to fix this problem.  As per the node I checked few things

node-2:~ # strace -f -o asm_discover.out /usr/sbin/oracleasm-discover 'ORCL:*'
Unable to open ASMLib

node-2:~ # ls -al   /opt/oracle/extapi/64/asm/orcl/1/libasm.so
ls: cannot access /opt/oracle/extapi/64/asm/orcl/1/libasm.so:
No such file or directory

So it was pretty clear that someone removed the required files (libasm.so in this case).  So I copied the files from working node.

node-1:/opt/oracle # scp -rp *  root@node-2:/opt/oracle
setasmgid             100% 2174KB   2.1MB/s   00:00
libasm.so             100%   75KB  75.2KB/s   00:00

 Now oracleasm was able to get to the disk

node-2:~ # strace -f -o asm_discover.out /usr/sbin/oracleasm-discover 'ORCL:*'
Using ASMLib from /opt/oracle/extapi/64/asm/orcl/1/libasm.so
[ASM Library - Generic Linux, version 2.0.4 (KABI_V2)]
Discovered disk: ORCL:DK65_1 [10361925 blocks (5305305600 bytes), maxio 512]
Discovered disk: ORCL:DK65_10 [10361925 blocks (5305305600 bytes), maxio 512]
Discovered disk: ORCL:DK65_11 [10361925 blocks (5305305600 bytes), maxio 512]
Discovered disk: ORCL:DK65_2 [10361925 blocks (5305305600 bytes), maxio 512]
Discovered disk: ORCL:DK65_3 [10361925 blocks (5305305600 bytes), maxio 512]
Discovered disk: ORCL:DK65_4 [10361925 blocks (5305305600 bytes), maxio 512]
Discovered disk: ORCL:DK65_5 [10361925 blocks (5305305600 bytes), maxio 512]
Discovered disk: ORCL:DK65_6 [10361925 blocks (5305305600 bytes), maxio 512]
Discovered disk: ORCL:DK65_7 [10361925 blocks (5305305600 bytes), maxio 512]
Discovered disk: ORCL:DK65_8 [10361925 blocks (5305305600 bytes), maxio 512]
Discovered disk: ORCL:DK65_9 [10361925 blocks (5305305600 bytes), maxio 512]
Discovered disk: ORCL:DK67_1 [10235904 blocks (5240782848 bytes), maxio 512]
Discovered disk: ORCL:DK67_11 [10235904 blocks (5240782848 bytes), maxio 512]
Discovered disk: ORCL:DK67_12 [10235904 blocks (5240782848 bytes), maxio 512]
Discovered disk: ORCL:DK67_13 [10235904 blocks (5240782848 bytes), maxio 512]
Discovered disk: ORCL:DK67_14 [10235904 blocks (5240782848 bytes), maxio 512]
Discovered disk: ORCL:DK67_15 [10235904 blocks (5240782848 bytes), maxio 512]
Discovered disk: ORCL:DK67_2 [10235904 blocks (5240782848 bytes), maxio 512]

I restarted ASM instance & disks were visible now in v$asm_disk.

Advertisements
This entry was posted in Oracle Automatic Storage Management and tagged . Bookmark the permalink.

6 Responses to Oracleasm disks not listed in v$asm_disk

  1. Kip West says:

    . root danaly oracleasm-discover .Using ASMLib from opt oracle extapi 32 asm orcl 1 libasm.so. ASM Library – Generic Linux version 2.0.0 KABI V2 .Discovered disk ORCL VOL1 39070048 blocks 20003864576 bytes maxio 128 .Discovered disk ORCL VOL2 39070080 blocks 20003880960 bytes maxio 128 .Discovered disk ORCL VOL3 39070080 blocks 20003880960 bytes maxio 128 .Discovered disk ORCL VOL4 25043040 blocks 12822036480 bytes maxio 128 …ASM . . oracle danaly kfed read dev oracleasm disks VOL1.kfbh.endian 1 0x000 0x01.kfbh.hard 130 0x001 0x82.kfbh.type 1 0x002 KFBTYP DISKHEAD.kfbh.datfmt 1 0x003 0x01.kfbh.block.blk 0 0x004 T 0 NUMB 0x0.kfbh.block.obj 2147483648 0x008 TYPE 0x8 NUMB 0x0.kfbh.check 851041336 0x00c 0x32b9dc38.kfbh.fcn.base 0 0x010 0x00000000.kfbh.fcn.wrap 0 0x014 0x00000000.kfbh.spare1 0 0x018 0x00000000.kfbh.spare2 0 0x01c 0x00000000.kfdhdb.driver.provstr ORCLDISKVOL1 0x000 length 12— .kfdhdb.driver.reserved 0 827084630 0x008 0x314c4f56.kfdhdb.driver.reserved 1 0 0x00c 0x00000000.kfdhdb.driver.reserved 2 0 0x010 0x00000000.kfdhdb.driver.reserved 3 0 0x014 0x00000000.kfdhdb.driver.reserved 4 0 0x018 0x00000000.kfdhdb.driver.reserved 5 0 0x01c 0x00000000.kfdhdb.compat 168820736 0x020 0x0a100000.kfdhdb.dsknum 0 0x024 0x0000.kfdhdb.grptyp 1 0x026 KFDGTP EXTERNAL– .kfdhdb.hdrsts 3 0x027 KFDHDR MEMBER.kfdhdb.dskname VOL1 0x028 length 4.kfdhdb.grpname ORADG 0x048 length 5– .kfdhdb.fgname VOL1 0x068 length 4.kfdhdb.capname 0x088 length 0.kfdhdb.crestmp.hi 32875626 0x0a8 HOUR 0xa DAYS 0x3 MNTH 0x9 YEAR 0x7d6.kfdhdb.crestmp.lo 3478022144 0x0ac USEC 0x0 MSEC 0x39a SECS 0x34 MINS 0x33.kfdhdb.mntstmp.hi 32875626 0x0b0 HOUR 0xa DAYS 0x3 MNTH 0x9 YEAR 0x7d6.kfdhdb.mntstmp.lo 3544465408 0x0b4 USEC 0x0 MSEC 0x110 SECS 0x34 MINS 0x34.kfdhdb.secsize 512 0x0b8 0x0200.kfdhdb.blksize 4096 0x0ba 0x1000.kfdhdb.ausize 1048576 0x0bc 0x00100000.kfdhdb.mfact 113792 0x0c0 0x0001bc80.kfdhdb.dsksize 19077 0x0c4 0x00004a85.kfdhdb.pmcnt 2 0x0c8 0x00000002.kfdhdb.fstlocn 1 0x0cc 0x00000001.kfdhdb.altlocn 2 0x0d0 0x00000002.kfdhdb.f1b1locn 2 0x0d4 0x00000002.kfdhdb.redomirrors 0 0 0x0d8 0x0000.kfdhdb.redomirrors 1 0 0x0da 0x0000.kfdhdb.redomirrors 2 0 0x0dc 0x0000.kfdhdb.redomirrors 3 0 0x0de 0x0000.kfdhdb.dbcompat 168820736 0x0e0 0x0a100000.kfdhdb.grpstmp.hi 32875626 0x0e4 HOUR 0xa DAYS 0x3 MNTH 0x9 YEAR 0x7d6.kfdhdb.grpstmp.lo 3477741568 0x0e8 USEC 0x0 MSEC 0x288 SECS 0x34 MINS 0x33.kfdhdb.ub4spare 0 0 0x0ec 0x00000000.kfdhdb.ub4spare 1 0 0x0f0 0x00000000.kfdhdb.ub4spare 2 0 0x0f4 0x00000000.kfdhdb.ub4spare 3 0 0x0f8 0x00000000.kfdhdb.ub4spare 4 0 0x0fc 0x00000000.kfdhdb.ub4spare 5 0 0x100 0x00000000.kfdhdb.ub4spare 6 0 0x104 0x00000000.kfdhdb.ub4spare 7 0 0x108 0x00000000.kfdhdb.ub4spare 8 0 0x10c 0x00000000.kfdhdb.ub4spare 9 0 0x110 0x00000000.kfdhdb.ub4spare 10 0 0x114 0x00000000.kfdhdb.ub4spare 11 0 0x118 0x00000000.kfdhdb.ub4spare 12 0 0x11c 0x00000000.kfdhdb.ub4spare 13 0 0x120 0x00000000.kfdhdb.ub4spare 14 0 0x124 0x00000000.kfdhdb.ub4spare 15 0 0x128 0x00000000.kfdhdb.ub4spare 16 0 0x12c 0x00000000.kfdhdb.ub4spare 17 0 0x130 0x00000000.kfdhdb.ub4spare 18 0 0x134 0x00000000.kfdhdb.ub4spare 19 0 0x138 0x00000000.kfdhdb.ub4spare 20 0 0x13c 0x00000000.kfdhdb.ub4spare 21 0 0x140 0x00000000.kfdhdb.ub4spare 22 0 0x144 0x00000000.kfdhdb.ub4spare 23 0 0x148 0x00000000.kfdhdb.ub4spare 24 0 0x14c 0x00000000.kfdhdb.ub4spare 25 0 0x150 0x00000000.kfdhdb.ub4spare 26 0 0x154 0x00000000.kfdhdb.ub4spare 27 0 0x158 0x00000000.kfdhdb.ub4spare 28 0 0x15c 0x00000000.kfdhdb.ub4spare 29 0 0x160 0x00000000.kfdhdb.ub4spare 30 0 0x164 0x00000000.kfdhdb.ub4spare 31 0 0x168 0x00000000.kfdhdb.ub4spare 32 0 0x16c 0x00000000.kfdhdb.ub4spare 33 0 0x170 0x00000000.kfdhdb.ub4spare 34 0 0x174 0x00000000.kfdhdb.ub4spare 35 0 0x178 0x00000000.kfdhdb.ub4spare 36 0 0x17c 0x00000000.kfdhdb.ub4spare 37 0 0x180 0x00000000.kfdhdb.ub4spare 38 0 0x184 0x00000000.kfdhdb.ub4spare 39 0 0x188 0x00000000.kfdhdb.ub4spare 40 0 0x18c 0x00000000.kfdhdb.ub4spare 41 0 0x190 0x00000000.kfdhdb.ub4spare 42 0 0x194 0x00000000.kfdhdb.ub4spare 43 0 0x198 0x00000000.kfdhdb.ub4spare 44 0 0x19c 0x00000000.kfdhdb.ub4spare 45 0 0x1a0 0x00000000.kfdhdb.ub4spare 46 0 0x1a4 0x00000000.kfdhdb.ub4spare 47 0 0x1a8 0x00000000.kfdhdb.ub4spare 48 0 0x1ac 0x00000000.kfdhdb.ub4spare 49 0 0x1b0 0x00000000.kfdhdb.ub4spare 50 0 0x1b4 0x00000000.kfdhdb.ub4spare 51 0 0x1b8 0x00000000.kfdhdb.ub4spare 52 0 0x1bc 0x00000000.kfdhdb.ub4spare 53 0 0x1c0 0x00000000.kfdhdb.ub4spare 54 0 0x1c4 0x00000000.kfdhdb.ub4spare 55 0 0x1c8 0x00000000.kfdhdb.ub4spare 56 0 0x1cc 0x00000000.kfdhdb.ub4spare 57 0 0x1d0 0x00000000.kfdhdb.acdb.aba.seq 0 0x1d4 0x00000000.kfdhdb.acdb.aba.blk 0 0x1d8 0x00000000.kfdhdb.acdb.ents 0 0x1dc 0x0000.kfdhdb.acdb.ub2spare 0 0x1de 0x0000…ASM ….Posted by eygle at .. ….. 1 3 ONLINE VOL4..6 rows selected…SQL create diskgroup orag2 external redundancy disk ORCL VOL5 ..Diskgroup created…SQL select group number disk number mode status name from v asm disk ..GROUP NUMBER DISK NUMBER MODE STATUS NAME.———— ———– ————– ————————————-.

  2. Admiring the hard work you put into your site and in depth
    information you provide. It’s good to come across a blog every once in a while that
    isn’t the same old rehashed information. Wonderful
    read! I’ve saved your site and I’m adding your RSS feeds to my Google account.

  3. This is very fascinating, You’re an excessively skilled blogger.
    I’ve joined your rss feed and stay up for in quest of extra of your great post.
    Additionally, I have shared your web site in
    my social networks

  4. vickyfin says:

    Hello Yogesh,

    I can discover the devices with /usr/sbin/oracleasm-discover ‘ORCL:*’, but when I change the asm_diskstring parameter to ‘ORCL:*’ and re-start ASM instance, it is not able to find disks.

    ORA-15032: not all alterations performed
    ORA-15017: diskgroup “LOG2” cannot be mounted
    ORA-15063: ASM discovered an insufficient number of disks for diskgroup “LOG2”
    ORA-15017: diskgroup “LOG1” cannot be mounted

    • This can be caused due to multiple reasons.

      Error: ORA-15063 ASM discovered an insufficient number of disks for diskgroup %s
      —————————————————————————
      Cause: ASM was unable to find a sufficient number of disks belonging to the diskgroup to continue the operation.
      Action: Check that the disks in the diskgroup are present and functioning,that the owner of the ORACLE binary has read/write permission to the disks, and that the ASM_DISKSTRING initialization parameter has been set correctly. Verify that ASM discovers the appropriate disks by querying V$ASM_DISK from the ASM instance.

      Check metalink note 1535996.1, for some more information. If that doesn’t help, I would suggest to open an Oracle service request.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s