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

Recovery If any updaters have not shutdown after the monitor has sent ABORT RDF
messages, then you might have to terminate the surviving updaters manually using a TACL
STOP command.
842
Error - START prevented by RDF TAKEOVER
Cause You issued a START RDF command, but the monitor detected that RDF has already
processed a TAKEOVER command.
Effect The START RDF command fails.
Recovery The backup database is consistent and ready for use as a backup contingency
database. Perform the rest of your installation-specific operations for switching to the backup
node (for example, reroute your communications and start your applications).
If you performed the TAKEOVER operation inadvertently, you will need to issue an INITIALIZE
RDF command and resynchronize the databases.
843
Incorrect version of audit received
Cause The receiver has received audit from the extractor that does not match the version
of audit that the receiver expects.
Effect The receiver abends.
Recovery This is an internal error. Contact your service provider.
844
Phase one database synchronization complete
Cause The updater that generated this message has completed phase one of the online
synchronization operation for its volume on the backup system.
Effect The updater starts phase two of the online synchronization operation.
Recovery This is an informational message; no recovery is required.
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.
RDF Messages 373