Since upgrading from 11.2.0.3 to 11.2.0.4 my ASMs lose contact the OCRVOTE Diskgroup.
A database that has been working flawlessly with loading TBs of data for several months crashed spontaneously two days after the upgrade, and this has now happened three times in ten days.Suddenly the control file copies on my +DATA and +FRA disk groups are not the same age and the database crashes with a warning on control file corruption.
Each time I got it working again after recreating the control file from the youngest copy and performing a full recovery.
The first time we saw the problem was when upgrading the SAN switches, the storage team took down one of two redundant network paths, brought it up again and did the same with the second path. After doing this on both nodes on a two node RAC, the voting disk group OCRVOTE was dismounted on both instances and were taken offline permanently, resulting in a cluster that was unresponsive but with both database instances up and running.
Each time I got it working again after recreating the control file from the youngest copy and performing a full recovery.
The first time we saw the problem was when upgrading the SAN switches, the storage team took down one of two redundant network paths, brought it up again and did the same with the second path. After doing this on both nodes on a two node RAC, the voting disk group OCRVOTE was dismounted on both instances and were taken offline permanently, resulting in a cluster that was unresponsive but with both database instances up and running.
0