Re: Q: Making sure 2nd instance contains same records

From: Joel Garry <joelga_at_rossinc.com>
Date: 1996/09/26
Message-ID: <1996Sep26.211308.6177_at_rossinc.com>#1/1


In article <32461476.238D_at_gnn.com> Gary Corsar <gecorsar_at_gnn.com> writes:
>I've been working on a simple solution to what should be a simple
>problem. How about some fresh ideas? Well, here's the problem. I've
>got Pro*C code that selects which db instance to connect to. This is
>in case the primary db is down, it can find a secondary db and still do
>it's job. It may also connect to the secondary if there is a network
>glitch and the primary really isn't down.
>
>I've got a trigger from the primary to the secondary to post transactions
>made to the primary table. My problem is, how do I make sure the two
>table always stay in sync. Even if a process connects to the secondary
>due to network problems.

It sounds like you want to have a column to specifically record the instance it was originally posted to.

>
>It gets worse when I consider that the primary may actually be off line
>and then the tables need to be brought back in sync when it gets back
>on line. I could probably do an initial snapshot or copy but that may
>not cover all situations.
>
>It sounds like Oracle 7.3 may have an answer to this with a new backup
>db scheme, but, I've got 7.2.3 now and will probably not upgrade until
>the software needs to go on line.
>
>If anyone's got a solution or knows where I might find some research or
>articles on this type of backup, I'd really appreciate it.
>
>Thanks!

-- 
Joel Garry               joelga_at_rossinc.com               Compuserve 70661,1534
These are my opinions, not necessarily those of Ross Systems, Inc.   <> <>
%DCL-W-SOFTONEDGEDONTPUSH, Software On Edge - Don't Push.            \ V /
panic: ifree: freeing free inodes...                                   O
Received on Thu Sep 26 1996 - 00:00:00 CEST

Original text of this message