JDBC with mulitple instances of database

gbhatti

Dear all,

Our application needs a bit of database redundancy.

Our application only accesses database for reading purposes.

We want to have two databases in separate machines. Incase one database
server dies the application should automatically extract data from the
other server.

Is there any JDBC driver available so that it can detect failure in the
main database server and then tries to extract data from the standby
database server?

Kind regards
--
Posted via http://dbforums.com

Jul 19 '05 #1

sybrandb

gbhatti <me*********@dbforums.com> wrote in message news:<34****************@dbforums.com>...

Dear all,

Our application needs a bit of database redundancy.

Our application only accesses database for reading purposes.

We want to have two databases in separate machines. Incase one database
server dies the application should automatically extract data from the
other server.

Is there any JDBC driver available so that it can detect failure in the
main database server and then tries to extract data from the standby
database server?

Kind regards

This functionality is available in sqlnet as transparent application
failover (TAF). If you use the ordinary jdbc driver you should be able
to use this without problem, providing you do your homework with
respect to standby databases and TAF and don't start experimenting
'somewhere'

Sybrand Bakker
Senior Oracle DBA

Jul 19 '05 #2

gbhatti

Thank you very much.

Could you elaborate bit more on "my homework". A link to more
information would suffice?

regards
--
Posted via http://dbforums.com

Jul 19 '05 #3

hrishy

Hi

Sarch for Transperent Application Failover (TAF)at tahiti.oracle.com
or in the documentation CD supplied by oracle.This functionality is
built into the net8 drivers as far as i know if you use thick JDBC
drivers the problem should be trivial.

You gotta understand what TAF does it only does sleect failover.So if
your transaction fails in the middle it will connect you to the next
redundant database and starts your transaction all over again..This is
imp.as failover does not mean that your transaction will continue
automagically from where it failed.

regards
Hrishy

Jul 19 '05 #4