This was due to a bug in the VxVM code whereby the internal Veritas Volume Manager file was refreshed to contain only the available ASM devices.

The workaround was to manually recreate the device entries using the vxdmpasm utility once the storage was back online.

 

This issue has been fixed in a number of patches such as 5.1SP1RP4 (Aix, Solaris, Linux) and 5.1SP1RP3P2 (HPUX)  and 6.0.5 cross-platform.

 

 

Oracle Automatic Storage Management (ASM) devices created using the vxdmpasm utility store an entry in an internal Veritas Volume Manager file. This internal file is needed for the auto-regeneration of these devices after reboot. During reboot this file will be updated with the ASM devices currently available in the system. However if a storage loss occurs and this is followed by a reboot of the system, the internal file will get cleaned up as there will be no ASM devices available during the reboot. As a result of this even when the devices are online once again, the auto-regeneration of the previously listed devices won't occur.

ETrack: 2556467