Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Usenet -> c.d.o.server -> Re: Snapshot of Data on a seperate database

Re: Snapshot of Data on a seperate database

From: <>
Date: Wed, 14 Jan 2004 08:21:51 -0600
Message-ID: <>

On Wed, 14 Jan 2004 00:27:12 GMT, "Gerry Sinkiewicz" <> wrote:

>"Ronnie" <> wrote in message
>> Hi,
>> We have 2 databases one internal OLTP database and another external
>> which our clients access.
>> We want to have a snapshot of the internal database on our external
>> database so that our clients can have read only access to the external
>> database.
>> I came up with the following solutions
>> Export the whole schema and import it into the external database. But
>> this has turned out to be a pain as I will have to drop the schema and
>> recreate it and then import the tables.
>> Implement views on the external database for each and every table in
>> the internal database, but this will increase the load on our internal
>> database and more important since our internal database is licensed on
>> Named user plus, every client of ours that connect to our database
>> will be a Named User. (Our external database is licensed on number of
>> processors but since views will access the internal database through
>> database links oracle treats these as Users)
>> Is there any other better solution to do this.
>> Maybe Replication....
>> Please suggest.
>> Thanks
>> Ron
>Snapshot, yes replication.
>Things called materialized views, used to be called snapshots (see create
>This does not even need advanced replication it is part of basic Oracle EE.
>It will solve the licensing issue.
>The only other solution would be to place the internal database on the
>outside (not recommended)
>on the same CPU licensed server, or bring the external DB inside and use
>and app (IIS) in a DMZ to access
>the data through a pinhole in the firewall or sql-proxy.

I've been doing what he requires using a set of scripts that clear the schema, import the primary database, and recompile all the objects. In my case, the original database has something like 400 tables - are materialized views really an option for this? I would love a faster way to handle the import process.

Harry Boswell Received on Wed Jan 14 2004 - 08:21:51 CST

Original text of this message