Re: Replication or Database Link ?

First problem:

With synchronous replication, if one database goes down, you can't do updates to the other until you either bring up the downed database or turn off the synchronous replication -- which brings up synchronizing problems when you finally fix the crashed database.

I assume one database is on the internet and one is on your internal LAN. How are you getting the connection across the firewall? what security are you implementing?

tsalzsie_at_my-deja.com wrote in message <7ots95$jes$1_at_nnrp1.deja.com>...
>Pete,
>
>thanks for your reply. There are some semantic as well as security
>reasons that we need two databases. The databases are in the same
>network (in other words in the same data center) and afaik are connected
>via a 100 Mbit network.
>One of the reason some people in our department tend to use synchronous
>replication is availability - in other words, WEBDB is still availabe
>when CALLDB crashes and vice versa. However, I'm not sure how to handle
>these large batch jobs at night - how replication reacts or if it makes
>sense to disable replication while these batch jobs are running.
>So, database links seems to be the most appropriate solution with
>respect to simplicity, reliability and performance.
>
>Any other recommendations or things we should look for ?
>
Received on Thu Aug 12 1999 - 09:59:48 CDT