This content has been marked as final. Show 5 replies
If you're using oracleasm then recreate the asm disks again.
http://sabdarsyed.blogspot.com/2007/07/installing-configuring-oracle-asm-on.html should help. (use only the delete and create commands no need to reinstall again)
HI,1 person found this helpful
can you try to drop and recreate disk group with same name DATA using DBCA ?
Hello. Thanks a lot for replying. That's right. The issue is solved. Thanks.
Hi, in case this helps anyone else. I got this INS-30516 error too was stumped for little while. I have 2 x 2-node RAC which are hitting same SAN. The first-built RAC has a DATA diskgroup. When went to build second RAC on new ASM disk new DIskgroup (but same diskgroup name DATA) got INS-30516 about diskgroup name already in use etc. Finally figured out all that was required was to restrict diskstring using button in installer to only retrieve the LUNS for this RAC (this was quick and dirty - all LUNS for both RAC being presented to both RAC). Once diskstring only searched for the LUNS required for this RAC only, e.g.
ORCL:DATA_P* (for DATA_PD and FRA_PD)
the error went away.
I also have DATA_DR and FRA_DR presenting to both RAC. Apparently it scans the header and if it finds a diskgroup name that is already in use based on the diskstring scan it will not allow reuse of the diskgroup name since it has no way of knowing that the other ASM disks are for a different RAC.
On Solaris we did like below to the raw devices and we could then see them as candidate disks :
dd if=/dev/zero of=c3t60A98000534B502F56346958786B7A67d0s3 bs=8192 count=20
use slice s3 only, s2 (slice 2) the whole disk. If you run it on that slice you will delete the VTOC (partitioning table) as well.