I can only second that email from Mark! Developing against single instance when prod is RAC - I can't count the number of times I have seen developers code against single instance Oracle (and maybe even a subset of production data only), release the new code which then promptly fails to scale/work in RAC? I dealt with an application development "framework" once that dynamically changed to "select for update" as soon as a user modified data. This was in a connection pool... That obviously wasn't too great. Also don't forget that you might actually _have_ to invoke DR and then you could be hit big time for not running in a RAC configuration. I only hope that has been figured into the equation or somebody from high up acknowledges that. Regards Martin -- Martin Bach OCM 10g http://martincarstenbach.wordpress.com http://www.linkedin.com/in/martincarstenbach On 02/03/2010 08:44 PM, Mark W. Farnham wrote: > So I believe your management dictated constraints are: RAC for prod, > single instance databases for everything else. > > -- //www.freelists.org/webpage/oracle-l