Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!news.linkpendium.com!newsfeed.stueberl.de!news2.telebyte.nl!lightspeed.eweka.nl!62.45.52.242.MISMATCH!newsfeed.kabelfoon.nl!195.129.110.21.MISMATCH!bnewsfeed00.bru.ops.eu.uu.net!bnewsinpeer01.bru.ops.eu.uu.net!bnewspost00.bru.ops.eu.uu.net!emea.uu.net!not-for-mail From: "Niall Litchfield" Newsgroups: comp.databases.oracle.server References: <5ddf960e.0312111124.2e8d770e@posting.google.com> Subject: Re: Multi-Master Replication over an air-gap Date: Fri, 12 Dec 2003 10:09:41 -0000 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Lines: 26 Message-ID: <3fd993e5$0$9386$ed9e5944@reading.news.pipex.net> NNTP-Posting-Date: 12 Dec 2003 10:09:41 GMT NNTP-Posting-Host: host9.audit-commission.gov.uk X-Trace: 1071223781 reading.news.pipex.net 9386 193.128.236.219:31278 X-Complaints-To: abuse@uk.uu.net Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:249958 I must be missing something here. If the 'security restrictions' mean that you cannot connect the two databases via an appropriate dblink then surely they prevent you just walking out of the server room with the data on disk. Surely there is something wrong with a business requirement that says these two databases must be synchronized and *at the same time* these two databases cannot be allowed to communicate. This is the issue I would address not exp/imp dumping to flat files and using sql*loader, going through an intermediary (pc with 2 connections) or whatever other technical workarounds to the base problem one might think of. -- Niall Litchfield Oracle DBA Audit Commission UK "Andrew Blakeslee" wrote in message news:5ddf960e.0312111124.2e8d770e@posting.google.com... > I am investigating a scenario where I need to keep two databases > synchronized, but there cannot be a physical connection due to > security constraints. Is it possible to setup a multi-master > replication scenario where the replication transactions are copied to > a removable media from one database and then loaded from the removable > media to the other database at fixed intervals? There should be a > relatively low volume of transactions, so the size of the data being > transferred should not be an issue.