Re: replication, export, or offline instantiation (2)

I think, a standard replication is most suitable. Just create snapshots on 2nd DB. Set refresh timing. That's practically it. Some tips:
Put all tables bind by reference constrains (FK) into one refresh group. Set refconstraints to be checked deffered.

What do you mean by "offline". You can have both DB disconnected (in terms of network) each other. You need to connect them for refresh procedure only (once in a month). But this should be real network connection (like TCP/IP). Offline floppy-net is impossible. Consider transportable TS.

Possible problems of nonfrecuent replication - big amount of data for monthly refreshes can create huge overloading on rollback segments. I'd consider more frequent refreshes - daily or hourly.

Mark Malakanov

J. Dupont wrote:

> Here is my problem. I have two data bases, the first one is made
> to produce documents, and the second is made to view documents.
> Main users add documents to the first DB. Once a month, the
> second DB is refreshed from the first DB. So, the new documents
> and modified documents are copied to the second DB, documents
> which are deleted in the 1st DB, are also deleted in the 2nd
> DB,... Main users can also add folders, classes or objects to
> the 1st DB, theses changes must also exist on the 2nd DB. The
> second DB contains some kind of documents that must not be
> changed. Moreover, I would like to use an offline device,
> because there is a lot of datas and the 2 DB are not connected
> (offline).
> So I would like to know your opinion about my problem. What is
> the best choice : replication ? explort/import ? offline
> instantiation ? transportable tablespaces ?
> Is it possible to do offline replication ? to refresh offline
> instantation ?
>
> Thanks in advance for your replies and your advices.
> Jérôme Dupont
>
>
>
Received on Thu Dec 06 2001 - 23:34:08 CST