RDF/IMP, IMPX, and ZLT System Management Manual

Messages
HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002
C-16
RDF Messages
736
error
is the file-system error number that identifies the specific error.
filename
is the name of the file that caused the error.
Cause. The updater could not obtain information about the specified file. Before an
updater can apply audit records to a file, it must obtain information about the file. The
probable reason why information could not be obtained is that the file has not been
created yet.
Effect. The updater delays for 30 seconds and then tries to obtain the information
again.
Recovery. If the specified file is an SQL table, then you must create that table on the
remote node.
If the specified file is an Enscribe file, the file may not exist on the RDF backup node
yet. If you have just created the file on the primary node, then the updater has
probably sent the creation audit record to the disk process, but the file has not yet been
created. In this case, this message is informational; when the file is created, the
updater will be able to obtain the information it needs and continue processing.
737
Cause. When the extractor is starting or restarting, it sends a request to the receiver
to obtain its starting position in the TMF audit trail. The extractor issues event 737,
indicating that the extractor is attempting to become synchronized with the receiver by
requesting this starting position.
Effect. The extractor attempts to become synchronized with the receiver.
Recovery. Informational message only; no corrective action is needed.
738
sno
is the sequence number of the TMF Master Audit Trail (MAT) for which the
synchronization point was established.
Waiting to obtain FILEINFO on file filename, error error
RDF extractor establishing synch
RDF extractor synch established SNO sno RBA rba