Re: ORA-15042: ASM disk "xx" is missing

From: Fergal Taheny <>
Date: Sun, 6 Jan 2013 20:27:20 +0000
Message-ID: <>

Hi Martin,
No it's not permissions. It's a san failure. Several disks have been lost and we are using external redundancy. Anyway my main aim was to find out if I could retrieve the list of asm disks including the device file paths off the disks. The missing disks were not appearing through the asm views. Well I managed to find a partial list. I would be fairly certain that the rest of the list is on one of the lost disks. And the list does not include the device file paths. So the only way to get this info is from the alert log the last time the disks were mounted. Or preferably document your config and kfod is useful for that.

The other thing worth nothing is the asm support guy's blog has some very good info.

On 6 Jan 2013 18:04, "Martin Berger" <> wrote:

> Fergal,
> Do you have root access and can check if /dev/oradsk/ASMDA3 exists and
> 'just' has wrong permissions? (or make your administrator to check?)
> I'd really follow your "sloppy administrator" theory.
> With root access you can also use kfed (as root) and check it's output.
> best regards,
> Martin
> On Thu, Jan 3, 2013 at 11:09 AM, Fergal Taheny <> wrote:
>> Hi,
>> I had tried kfed but not kfod. Still no joy the 5 missing disks don't show
>> up.
>> > kfod asm_diskstring='/dev/oradsk/*' disks=all
>> --------------------------------------------------------------------------------
>> ...
>> See here.
>> Not much use though. Yes there are some errors like this
>> 13522: stat("/dev/oradsk/ASMDA3", 0xFFFFFFFF7FFFCCC0) Err#2 ENOENT
>> Now we know that /dev/oradsk/ASMDA3 is indeed one of the missing disks as
>> per the old alert log. But all that the truss proves is that the process
>> can't read from these devices that it finds in the asm_diskstring. These
>> could just have been devices that were just left behind by a sloppy
>> administrator!

Received on Sun Jan 06 2013 - 21:27:20 CET

Original text of this message