Oracle RAC running mad

Excerpt:

CRS is used in conjunction with Oracle's Real Application Clusters 
software, which allows one Oracle database to be deployed on a group 
of servers or "nodes," providing fault tolerance and scalability.

The "leap second event" is causing CRS nodes to reboot, according to 
an Oracle document detailing the problem. Among the affected platforms 
are Oracle Server Enterprise Edition Version 10.1.0.2 to 11.1.0.7; 
Sun Solaris SPARC (64-bit); and Oracle CRS and patchsets 10.2.0.1 to 
11.1.0.7. 

I thought that one of the main reasons for setting up a database cluster is to increase availability and fault tolerance. It seems that Oracle missunderstood that :-) So what is the real meaning of the RAC abbreviation ?:

Reboot Automatically (and) Continuously

Not very pleasant for companies that run highly critical systems on Oracle RAC.

• InfoWorld: 'Leap second' snafu affects Oracle clusterware

BTW, on IBM developerWorks you'll find an interesting article about setting up 2-Node-Cluster with IDS thru Microsoft Cluster Server (MSCS). The article is written by Thomas Matthae who is the team leader of the SAP/Informix porting team.

• IDS and ClusterIT - How to set up Informix in a MSCS environment

If you've more confidence in the Linux operating system than in Microsoft, take a look at the IDS Resource Agent for Linux-HA Clustering.