I'm not sure what do you mean by word "Developers". If these are just plain coders building sql/pl/sql/whatever code according to spec then probably RAC is not so significant. On the other hand normally for new systems there is such a role like system architect. He has to think about the app and avoid serialization points (for example sessions table which is modified after each request from ten nodes for hundreds/thousands of users) as much as possible. DBAs later can somehow leverage the harm already done trying to tune table's physical attributes etc etc, but he has quite limited possibilities to do that. If the system architect/lead developer/whatever we call him wouldn't chose exactly this solution life would be easier for all people later. So probably DBAs don't need to go in cubicle of each of 5/10/100 developers, but he definitely HAS TO GO in cubicle of the system architect and tell him what RAC really needs and what to avoid, unless system architect already knows that. And then system architect/lead developer HAS TO model the app and create system architecture avoiding possible serialization points. If system architect is not doing that alone then all significant persons should be warned and know about consequences of RAC. Gints Plivna http://www.gplivna.eu 2010/5/19 Yong Huang <yong321@xxxxxxxxx>: > --- On Wed, 5/19/10, D'Hooge Freek <Freek.DHooge@xxxxxxxxx> wrote: > Everything else you or others say is the work of DBAs and app server admins. > Developers don't need to do anything. This may be difficult to understand > because most Oracle-L members are DBAs (with prior experience of > development). If you ask How can a developer login the app server or even > database server to modify a config file?, then it's easier to understand. Or > imagine a DBA going to a developer's cubicle and tell him, "We're running > RAC, dude. So please change this part of code." > > Yong Huang -- //www.freelists.org/webpage/oracle-l