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

Recovery For partitioned files and files with alternate keys, if any partition or alternate key
file is on a volume protected by RDF, then all partitions and alternate key files must be on
volumes protected by RDF.
Either the file must be redefined on the primary node, or the other volume must be made
protected by RDF. In the latter case, the backup file must then be resynchronized with the
primary file.
741
RDF extractor message out of order
Cause The receiver has received a message from the extractor that is out of order. When
this event occurs, the extractor automatically reestablishes synchronization with the receiver.
If the extractor has several outstanding requests to the receiver and the first is found to be out
of order, the receiver rejects each subsequent request with this same error. When the extractor
reestablishes synchronization, normal processing resumes.
Effect The receiver directs the extractor to reestablish synchronization.
Recovery This is an informational message; no recovery is required.
742
RDF extractor internal audit read error. File filename RBA rba
filename
is the name of the audit-trail file that contained the error.
rba
is the relative byte address where the error occurred in the audit-trail file.
Cause The extractor encountered an error in audit processing.
Effect The extractor abends, thereby stopping the other RDF processes.
Recovery Save the SAVEABEND file, the audit-trail file, and contact your service provider.
You must reinitialize RDF.
743
Catastophic error encountered
Cause A fatal error occurred in RDF.
Effect RDF stops.
Recovery Restart RDF and contact your service provider.
744
FILEINFO obtained on [ANSI-object-type ANSI-name, Partition
partition-id,] file filename
ANSI-object-type
is the ANSI object type (for example, table, index, and so on.). See Table 16-1 (page 295) for
a list of possible ANSI object types.
ANSI-name
is the ANSI name of the SQL/MX object that encountered the error.
partition-id
is the partition ID of the SQL/MX object that encountered the error.
filename
is the Guardian file name of the file that encountered the error.
Cause The updater was previously delayed in obtaining information about the specified
object. See RDF error 736. The information has now been obtained.
Effect The updater continues processing.
Recovery This is an informational message; no recovery is required.
RDF Messages 353