Strategies for redundant databases

We have a requirement for a distributed database in which three concurrent, identical copies of the tables will be maintained. This means that updates at any given location need to be written to all three databases simultaneously ( with two phase commit).

I am looking at two possible approaches:

1. Use of triggers and stored procedures (PL/SQL) for each of the tables. The stored procedures would have to be "smart" enough to handle the situation when one of the redundant database was unavailable. (Resynchronizing the databases could be performed off line.)
2. Handle the multi-database updates in the application using embedded SQL (PRO*C).

If anyone has done this sort of thing, I would appreciate ideas as to which approach is preferable.

Thanks
Peter Schauss
pschauss_at_aol.com
ps4330_at_okc01.rb.jccbi.gov
Gull Electronic Systems Div.
Parker Hannifin Corp
Smithtown, NY Received on Sat Oct 07 1995 - 00:00:00 CET