Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to know how the failover database concept works after recovery. We have defined our application to connect to a backup database in case the production database fails. If this happens, then all the transactions will be happening on that backup database. Once the production db server is running again, then how do we make sure the changes made in the backup database will be reflected on the production database? We want to make sure that any changes made while failed over are not lost. We are using Oracle 10g.

share|improve this question

What are you doing for replication? We're using a two way streams replication, so we just wait for the main database to get back up to date and then switch connections back.

share|improve this answer
@JOTN...I'm not sure what two way streams replication means and what we are currently doing. It was written by someone else and I am working on few modifications. Currently the failover database location is defined in tomcat's server.xml "Resource" element. <Resource name="or_ds" type="javax.sql.DataSource" auth="Container" url=";failover=true&amp;host1=YYYY‌​;port1=1530&amp;;port2=1530" password="a" maxActive="4" maxWait="5000" diverClassName= "com.inet.ora.OraDriver" username="legalusr" maxIdle="2" /> – rrkwells May 11 '11 at 16:00

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.