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" <andrew_at_soft-solutions-inc.com> wrote in message
news:5ddf960e.0312111124.2e8d770e_at_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.
Received on Fri Dec 12 2003 - 04:09:41 CST
