||Oracle Replication Tips by Burleson
Offline instantiation allows you to create the master group object
on the remote sites and then place replication on top of those
objects. While this method can greatly speed up the creation or
loading of replication objects, it is not without its own issues.
The base objects must be read-only from the time the data begins
moving until replication can assume control. If the base tables are
updated, then the copy will not be in sync.
mechanics of offline instantiation are simple, the execution is
not. Basically, you create your master group with false “copy_rows”.
This tells the master group to use the rows already at the remote
site. No data checks are performed. If the tables are not in sync,
then they will begin replication out of sync and stay that way.
Now comes the hard part. How
do you get the data to the remote site? The difficulty is that the
base tables must remain in read-only state until transfer is
gname => '"GROUP1"',
type => 'TABLE',
oname => '"BOOK"',
sname => '"PUBS"',
copy_rows => FALSE,
use_existing_object => TRUE);
This is an
excerpt from Oracle Replication By Rampant TechPress (only $19.95).
You can click here to order a copy and get instant access to the code
Get a Personal Oracle
The author is now offering personal mentors for
Oracle DBAs where you can have an Oracle expert right at your
fingertips, anytime day or night. We work with hundreds of Oracle
databases every year, so we know exactly how to quickly assist you
with any Oracle replication question.
You can get me personally, or any Oracle Certified replication DBA
with more than 20 years of full-time IT experience.