RE: Documentation for reasons to NOT use RAC?
- From: D'Hooge Freek <Freek.DHooge@xxxxxxxxx>
- To: Yong Huang <yong321@xxxxxxxxx>, Tony Adolph <tony.adolph.dba@xxxxxxxxx>
- Date: Wed, 19 May 2010 15:31:30 +0200
Hi,
Sorry, but I don't agree.
The developer is the one responsible for enabling the application to use
different connection pools with different connection strings. And he/she must
also be aware of which execution plans the statements are using (also very true
for single instances).
They don't need to login to the application server or change a config files for
that.
In my opinion, regardless if the database is on rac or not, the developers need
to know how the application will interact with the database and how to write
optimal code for these interactions. The dba can (must) assist them in doing
so, but they can't look at the database as just a black box.
Rac adds some more difficulty to how to code optimal and therefore the
developers must know in advance if the application will (maybe) run on rac or
not.
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
-----Original Message-----
From: Yong Huang [mailto:yong321@xxxxxxxxx]
Sent: woensdag 19 mei 2010 15:03
To: Tony Adolph; D'Hooge Freek
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: Documentation for reasons to NOT use RAC?
--- 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.
D'Hooge,
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
--
//www.freelists.org/webpage/oracle-l
Other related posts:
