RDF/IMP and IMPX System Management Manual (RDF 1.4+)

Messages
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
C-50
RDF Messages
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
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
Cause. The extractor has sent the maximum number of messages to the receiver and
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 the primary and backup systems to stop the RDF processes in an orderly fashion.
849
Cause. TMF was stopped during an RDF online database synchronization operation,
before the extractor had completed its phase one processing.
Effect. The extractor abends because the database synchronization operation can no
longer succeed.
Recovery. You must reinitialize the RDF product and restart the online database
synchronization operation.
RDF TAKEOVER during initialization synchronization
RDF extractor waiting for network reply
TMF Shutdown before phase one of database synchronization