RE: Documentation for reasons to NOT use RAC?

  • From: Yong Huang <yong321@xxxxxxxxx>
  • To: Tony Adolph <tony.adolph.dba@xxxxxxxxx>, D'Hooge Freek <Freek.DHooge@xxxxxxxxx>
  • Date: Wed, 19 May 2010 06:02:50 -0700 (PDT)

--- On Wed, 5/19/10, D'Hooge Freek <Freek.DHooge@xxxxxxxxx> wrote:
> Yong,
> For an application to realy benifit rac, the developers
> have to make it aware of fan.
> There are some prerequisites on the java classes to be used
> and statements should be retried when a failover happens.


Thanks for pointing that out. That's the point I thought of right after I sent 
my last message. And I believe that's the only thing *developers* can do when 
told they're connected to RAC.

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


Other related posts: