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

Messages
HP NonStop RDF/IMP and IMPX System Management Manual524388-001
C-29
RDF Messages
779
Cause. The extractor has terminated normal processing as the result of a STOP TMF
or STOP RDF command.
Effect. Normal RDF shutdown processing continues.
Recovery. This is an informational message; no recovery is required.
780
filename
is the name of the exception file.
Cause. An updater is unable to apply image records for some transactions because a
TAKEOVER command was executed and the commit, abort, or data records for the
transactions were not sent to the backup node. The message includes the name of the
exception file containing information about the image records that were not applied.
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. This is a normal occurrence during TAKEOVER processing. The system
manager 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 node might
not be applied to the backup database.
781
Cause. The extractor’s transaction status table that is used for online synchronization
has overflowed. This means that more than 650,000 transactions were started during
the first TMP control point interval following the RDFCOM STOP SYNCH command,
and those transactions are still active.
Effect. The extractor abends.
Recovery. You must initialize RDF to a new database synchronization timestamp and
then restart the entire operation from the beginning.
Local RDF extractor shutdown complete
Warning - Unapplied image record info in file filename
RDF extractor transaction status table overflow