Following reasons springs to mind: . Rac costs money. Not only for the licenses, but it also costs more time to maintain them (patching and stuff) and you need more experienced dba's to operate them (otherwise you would have more downtime due to human errors). . Not all applications benefit from RAC, both in terms of high availability and scalability. If you have for instance an application which mainly focuses on 1 table (and doing full table scans on it), it will not scale on RAC. Also, when your application can not cope with sessions being disconnected and restart on a different node (eg no support for fcf), then the high availability will be limited. . The database is just not important Regards, Freek D'Hooge Uptime Oracle Database Administrator email: freek.dhooge@xxxxxxxxx tel +32(0)3 451 23 82 http://www.uptime.be disclaimer: www.uptime.be/disclaimer ________________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of TESTAJ3@xxxxxxxxxxxxxx Sent: maandag 22 februari 2010 13:52 To: oracle-l@xxxxxxxxxxxxx Subject: Documentation for reasons to NOT use RAC? I'm being pulled into a meeting later this morning to answer why we shouldn't put every db in RAC? Any white papers etc, stating why its a bad idea? thanks, joe _______________________________________ Joe Testa, Oracle Certified Professional Senior Engineering & Administration Lead (Work) 614-677-1668 (Cell) 614-312-6715 Interested in helping out your marriage? Ask me about "Weekend to Remember" -- //www.freelists.org/webpage/oracle-l