My Oracle Support Banner

Disks Added to the ASM From One Node Are Not Discovered on the Other Node (Doc ID 400005.1)

Last updated on MARCH 22, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.5 and later
Information in this document applies to any platform.
***Checked for relevance on 06-Jan-2014***

Symptoms

Using RAC with ASM. New devices have been added to the diskgroups on one of the node without problems.
Unfortunately, the disks are not visible on the other node and trying to start the instance fails with errors like:
ORA-15042: ASM disk "19" is missing
ORA-15042: ASM disk "18" is missing
The ownership and permissions on the disks are given correctly and the nodes can be seen in /dev, but kfod does not report the new disks that have been added - equally they cannot be seen in v$asm_disk. 

truss the kfod utility as follows

truss -aefo kfod.txt kfod disks=all


The results would be similar to the ones below:

561196: access("/dev/rhdiskpower19", 06) = 0
561196: statx("/dev/rhdiskpower19", 0x0FFFFFFFFFFFD320, 176, 010) = 0
561196: open("/dev/rhdiskpower19", O_RDONLY|O_LARGEFILE) Err#16 EBUSY
561196: open("/dev/rhdiskpower19", O_RDONLY|O_LARGEFILE) Err#16 EBUSY


for all the problematic disks

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.