RDF System Management Manual for H-Series RVUs (RDF 1.8)

is stored in all image trails by the receiver). All transactions that might have been started during
the create/load or backup operations are now finished.
NOTE: TMP control points are generated as the result of transaction activity. For high rates of
transaction activity, the TMP control points might be only 1 or 2 minutes apart. For lower rates,
they might be 5 to 10 minutes apart. On a completely idle system, TMP control points can be
approximately 30-60 minutes apart. Therefore, if your applications and TMF are idle or nearly
so, it could take an hour or more for the extractor to encounter two TMP control points.
Upon completion of phase 1, part 3, the extractor logs message 768.
Phase 2
Phase 2 completes when the extractor is certain the synch-complete image record has been
successfully written in all image trails, and the extractor’s restart location is at a point in the audit
trail following the TMP control point record associated with the completion of phase 1, part 3,
above.
Upon completion of phase 2, the extractor logs message 782.
Updater Phase 2
You cannot start the updaters until the extractor has completed phase 2.
NOTE: If you are replicating only the Master Audit Trail (MAT), you can start the updaters as
soon as the extractor issues its 782 event message. If you are also replicating one or more auxiliary
audit trails, however, you must also wait for all of the auxiliary extractors to report 0:00 RTD
times before starting the updaters.
Phase 2 completes when the updater encounters the synch-complete image record in the
image trail. At that time the updater has processed all audit information that might have been
generated during the load or backup operation, and synchronization is complete for the associated
database volume.
Upon completion of phase 2, the updater logs message 782.
Extractor Restart Considerations During Online Database Synchronization
A number of circumstances can cause the extractor to restart during online database
synchronization, such as a primary CPU failure affecting either the extractor or receiver process.
Whenever the extractor encounters a restart condition it automatically recovers and resumes its
synchronization functions. Where it resumes, however, depends upon where it was when the
restart condition occurred.
• If the restart condition occurs prior to the start of phase 1, the extractor resumes wherever
the receiver tells it to.
• If the restart condition occurs after phase 1 has begun, the extractor might choose to resume
at an earlier position than the receiver tells it to. It does this to ensure that it has handled all
committed and aborted transactions correctly. If the extractor does resume at an earlier
position, it logs message 775. Additionally, regardless of whether or not it adjusted the
restart position, the extractor can log messages 766, 767, and 768 again, even if it had logged
any of them prior to the restart condition.
Determining When Online Database Synchronization Is Complete
The following RDF messages assist you in knowing when the various phases of online database
synchronization are complete:
170 Online Database Synchronization