HP NonStop RDF J-series RVUs Management Manual page 384

Effect If all the records for a transaction are not received on the backup node, the transaction
is treated as if it aborted. For every image record that is not applied to the backup database,
an exception record is written to the designated exception file.
Recovery
can use RDFSNOOP to list the image records that were not applied to the backup database.
The backup database will be consistent after the TAKEOVER operation, but some transactions
that might have committed on the primary system might not be applied to the backup database.
781
RDF extractor transaction status table overflow
Cause
The extractor's transaction status table that is used for online database synchronization
operations has overflowed. This has happened because more than 650,000 transactions were
started during the first TMP control point interval following the RDFCOM STOP SYNCH
command, and these transactions are still active.
Effect The extractor abends.
Recovery
restart the entire operation from the beginning.
782
Phase two database synchronization complete
Cause Phase two of the database synchronization involving the process generating this
message has completed.
Effect
If the process is the extractor, then all operations performed by the extractor for the
database synchronization are complete, although the updaters might not have completed their
work on the backup system.
If the process is an updater, then the backup database is synchronized for the volume protected
by the particular updater.
Recovery
783
RDF receiver process is not running
Cause
The monitor or extractor process could not open the remote receiver process after a
communications failure.
Effect If the monitor or extractor process receives a file-system error 14 (process does not
exist), RDF will shut down on the primary node.
Recovery
communications lines were down, simply restart RDF by issuing a START RDF command.
784
Shutdown pending STOP UPDATE, TIMESTAMP timestamp
timestamp
is the specified timestamp.
Cause The process has received notice that an RDFCOM STOP UPDATE, TIMESTAMP
command was executed.
Effect
Each updater applies only audit data associated with transactions that committed
prior to the specified timestamp.
Recovery
785
Redo pass ending on reaching timestamp timestamp
384 Messages
This is a normal occurrence during TAKEOVER processing. The system manager
You must initialize RDF to a new database synchronization timestamp and then
This is an informational message; no recovery is required.
If RDF was stopped on the remote node by a STOP RDF command while the
This is an informational message; no recovery is required.