This content has been marked as final. Show 4 replies
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DATA1"all disk are not available which required for DATA1 DG.
Is this parameter properly set at asm level? check alert log to crosscheck parameters when asm was running fine.
error in identifying file '+DATA1/zidw/spfilezidw.ora'try to bringup the asm with correct spfile.
An ASM diskgroup consists of 1 or more disks (raw devices, SAN LUNs, etc).
An externally redundant diskgroup needs all the disks of that diskgroup to be available for use. Data is stripped across all disks. So if any 1 disk is not available, that diskgroup cannot be used.
A normal or high redundant diskgroup is mirrored. In this case, all the disks in a single failgroup needs to be available for that diskgroup to mount. Such a diskgroup can run on a single failgroup (one part of the mirror).
If your DATA1 is normal or high redundancy, and all the disks of a failgroup is available, you can force DATA1 to mount.
If you do not have an intact failgroup, or intact externally redundant diskgroup, the diskgroup cannot be mounted.
Reasons for why specific disks for a diskgroup are not available, varies. It could be a permission issue. It could be that the device's name has changed. It could be a SAN or storage array issue. Etc.
You need to determine:
a) the name(s) of the missing disk(s) that ASM needs for that diskgroup
b) why those disks are not being made available by the kernel (looking at +/var/log/messages+ for example for device errors)
check the asm_disk_string parameter,
and check as well the permissions on your disks.
either the permissions where changed (like after a reboot), or the devices changed names.
also you should have an init file, startup the asm instance with the pfile.
pls take a look this doc