Something about licensing. Boring for the most of us, but this may save you a lot of money…. The next is not completely new, but I never had it on writing, so found it worthfull to blog. The following has by the way no legal status and I’m not held responsible […]
The second and final post about an issue with a RAC-configuration with two SAN's. Problem was a i/o-freeze of minutes when crashing one of the two SAN's. The first post I ended with a 'cliffhanger' because we had a solution, but not tested it yet.
Since 220.127.116.11 there's a new parameter, "_datafile_write_errors_crash_instance" to prevent the intance to crash when a write error on a datafile occurs. But.. should I use this or not.
With this setup we are facing the issue that if we loose a complete SAN, the IO’s to the ASM diskgroups will be blocked for approx 3 till 4 minutes. Oracle does not like this. After 70 seconds after a freeze, rdbms is starting to reboot (expected behaviour).
Red Hat 6 has been there a while, so what about certification with Oracle? Nothing on the Oracle support site, no press releases (maybe I missed one..). But Red Hat finally gave the answer in her Red Hat news - blog
Using rdbms 11.2 as the repository for our Grid Control environmont, noticed a lot of the same errors in the alert file of the repository or/and the target database:
NI cryptographic checksum mismatch error: 12599.
TNS for Linux: Version 18.104.22.168.0 – Production
Oracle Bequeath NT Protocol Adapter for Linux: […]
This is the second post of my little project of building my own RAC on my Windows7-desktop (64-bits, 8GB RAM), using 3 VM’s (VM-workstation , 7.1.3 build-324285) : * 2 VM’s for two RAC-nodes, based on OEL 5.5, 22.214.171.124 for infra, and database. * 1 VM as my own SAN, based on Openfiler 2.3 (free), for ASM.