Sunday 18 May, 2008 - 21:12
The problem described in Richmond Database (04) appears to have been caused by an issue with the Ethernet emulation in VMware. This was fixed by a complete restart of the YAOCM team.
That restart worked satisfactorily except that Oracle Enterrpise Manager was not able to access operating system metrics on richmond1. At least, the RAC came up.
When I did another restart, the ora.richmond1.ons resource failed to come online for richmond1. This precluded the initialisation of the CRS stack there. The crs stack was working on richmond2 but the oracle instance failed to come up.
I hope this is not another VMware issue.