||Oracle Replication Tips by Burleson
Loading or Re
So far, we have discussed moving large amounts of data before creating
the replication environment. Now you may ask, what if
replication has already been
created and is
running? You can always stop replication activity on the master group,
but that places all objects in the group in read-only status. To stop
replication and not place the objects in read-only status, you must use
This disables all replication triggers so that you can modify data
without replicating the changes. You can now load or remove data
without propagating the changes. When finished, reactivate the
Once the replication triggers are active, further changes will be
propagated. As always, there is a catch. It is up to the DBA to
insure that no user changes are made to any site while the
replication triggers are off. Also, to insure data integrity, all
sites should load the data simultaneously to avoid
conflicts. Data conflicts are discussed in the next chapter.
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.