RE: maintaining a backup table on another server

From: Jacques Kilchoer <Jacques.Kilchoer_at_quest.com>
Date: Mon, 19 Mar 2001 12:43:36 -0800
Message-ID: <F001.002D0CFB.20010319110554@fatcity.com>

See my answer below.

> -----Original Message-----
> From: john.armani_at_us.abb.com [mailto:john.armani_at_us.abb.com]
>
> We have a single table that contains audit information, and
> would like to
> create an identical table on a separate server that we will
> update at the
> same time we update the primary server table.   Multiple
> primary servers
> could exist throughout the system, and a common backup server could be
> shared by multiple primary servers.  The inserts, updates, and deletes
> would be done from pro*c library routines that would exist on client
> machines.
>
> A simple solution would be to create a database link to the
> backup table, and
> whenever we update the primary table we will send a second update to
> the backup table (via the database link).  This approach
> works fine as long
> as the servers are up, but raises issues in the case if one
> or both is down
> at update time.
>
> What other alternatives can we look into?  Is the Parallel
> Server concept an
> overkill?

If I understand your situation correctly, you want an application to update two tables in two different Oracle databases (that we will call A and B).

If you use a database link from A to B, when A is down, this will prevent both updates, which is your concern. Why not have the application open two different connections - one to A and one to B? I'm pretty sure that it's possible in Pro*C.

---

any ignorant comments made are the sole responsibility of J. R. Kilchoer and should not reflect adversely upon my employer.

 
Jacques R. Kilchoer
(949) 754-8816
Quest Software, Inc.
8001 Irvine Center Drive
Irvine, California 92618
U.S.A.
http://www.quest.com Received on Mon Mar 19 2001 - 14:43:36 CST