RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

845
Initialization synchronization completed
Cause
The updater that generated this message has completed its synchronization work for RDF
initialization to an initialization timestamp.
Effect
The updater resumes its normal processing.
Recovery
This is an informational message; no recovery is required.
846
RDF TAKEOVER during database synchronization
Cause
When the updater completed its RDF Takeover operation, it had not yet completed its role in an
online database synchronization.
Effect
The database might not be in a consistent state.
Recovery
There is no recovery. If you lose your primary system during an online database synchronization,
the backup database has not yet been synchronized, and its data therefore might not be
consistent.
847
RDF TAKEOVER during initialization synchronization
Cause
When the updater completed its RDF Takeover operation, it had not yet completed its role in an
INITIALIZE RDF...INITTIME operation.
Effect
The database might not be in a consistent state.
Recovery
There is no recovery. If you lose your primary system while the updaters are trying to catch up
from an INITIALIZE RDF...INITTIME operation, the backup database has not yet been
synchronized, and the data in it therefore might not be consistent.
848
RDF extractor waiting for network reply
Cause
The extractor has sent the maximum number of messages to the receiver and it has not received
any replies for at least five minutes.
Effect
The extractor cannot proceed any further.
Recovery
This is not an RDF problem. You should investigate your Expand network and take corrective
action. If necessary, you can issue a STOP RDF command on both primary and backup systems
to stop the RDF processes in an orderly fashion.
849
TMF Shutdown before phase one of database synchronization
RDF Messages 387