Home » Server Options » Replication » Problem in first time refresh of huge table in replication:
Problem in first time refresh of huge table in replication: [message #75072] Thu, 12 July 2001 10:50 Go to next message
Messages: 55
Registered: July 2000
1. What do I want to do?
I want to create a readonly snapshot
of a table called big_table which has 75 million rows.

2. Scenario
Master site : Oracle Enterprise Edition
on Windows NT
Snapshot site: Oracle Enterprise Edition
on Windows NT

I want to have only one master site and only one
snapshot site. Please note, OLite is not involved
anywhere in my setup.

3. Main Concern:
The table at master site is very huge
(75 million rows).

4. What is working?
Normal read-only snapshot works for small tables.

5. How do I want to address this issue:
I want to avoid getting data to the snapshot site
using conventional dblink for the first time
refresh, because of the huge volume of data,
dblink fails.

I think that using deployment template and offline
instantiation would be ideal for my case since it
will allow me to export tables from Master site
and import them at Snapshot site.

Unfortunately, there is very little documentation
and examples on deployment templates.

I want a sample which shows
- the kind of replication setup needed at both
sites.(advanced replication setup to be
done temporarily ?? )
- propogator and receiver setup to be done ??
- the script to do the first time refresh
- how to handle subsequent refreshes


Re: Problem in first time refresh of huge table in replication: [message #75079 is a reply to message #75072] Thu, 26 July 2001 20:11 Go to previous message
andrew again
Messages: 2577
Registered: March 2000
Senior Member
Take a look at transportable tablespaces as an alternative.

Previous Topic: RE: Trigger in Replicated Database
Next Topic: Oracle Image Replication - In Need Of An Expert!!!
Goto Forum:

Current Time: Fri Oct 23 01:27:06 CDT 2020