When you use bulk materialization, you must:
Unload the source data at the primary site
Move unloaded data to the replicate servers
Load data into the replicate tables
Apply updates made at the primary site after the media unload is performed
Replication Agent for DB2 does not support use of the
DB2 LOAD LOG YES utility to assist in replicate
materialization.
Three bulk materialization methods are available. The method you use depends mainly on whether one of the following conditions exist at your site:
A copy of the data already resides at the replicate site
Applications using the primary data can tolerate interruptions
The following table summarizes bulk materialization methods:
Bulk materialization method |
Summary of materialization process |
|---|---|
Subscription data already exists in the replicate database |
If the subscription data already exists at the replicate site, you must verify that it is consistent with the primary data and then define, activate, and validate the subscription. |
Atomic materialization |
This method prevents client applications from executing transactions against the primary data while the subscription data is unloaded. After defining the subscription, lock the primary data, retrieve the subscription data, activate the subscription, and unlock the primary data. Use this method to retrieve data from the primary database, if you are able to suspend updates to the primary data. |
Nonatomic materialization |
This method allows client applications to execute transactions against the primary data while the subscription data is unloaded. If you use this method, the data at the replicate database may be inconsistent with the data at the source database. Use this method only if you are unable to suspend transactions on the source database. |
