The connections have to be RAC aware. Most developers just connect to one instance instead of to all of them. Use of parallel in queries to take advantage of the Rac power. Writing custom apps as services are just a few things that come to mind. K --- On Tue, 2/23/10, Yong Huang <yong321@xxxxxxxxx> wrote: From: Yong Huang <yong321@xxxxxxxxx> Subject: RE: Documentation for reasons to NOT use RAC? To: ganstadba@xxxxxxxxxxx Cc: oracle-l@xxxxxxxxxxxxx Date: Tuesday, February 23, 2010, 11:36 AM > Not mentioned is I think RAC requires a commitment from developers > to program apps with RAC in mind. I find more and more that people Michael, Are you referring to application server admins? I don't see how developers should write code differently if the code needs to be deployed to RAC. Yong Huang -- //www.freelists.org/webpage/oracle-l