||Oracle Replication Tips by Burleson
Moving Large Oracle
Replication propagates data one change at a time. If you insert 300
rows into a replicated table, those 300 rows are propagated and
applied one row at a time to insure data integrity.
Oracle supports parallel propagation across the database links, but
the rows must be inserted at each master site in order. This is not
a problem for even relatively high transaction rates on OLTP systems.
if you load a million rows of data, it could take hours or days to
propagate. As if that were not bad enough, the table that you load
the data into will be read-only until the propagation is completed.
Another example is in the replication of the PUBS schema. If that
schema contained millions of rows of data, the replication creation
could take days. There must be a better way to load data into a
replicated table. There is, and it is called offline instantiation.
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.