RDF System Management Manual for H-Series and J-Series RVUs (RDF 1.9)

• To compare MAT positions in preparation for the RDFCOM COPYAUDIT command of
the triple contingency protocol
• To use for File Recovery to a MAT position on the primary system
Recovery This is an informational message; no recovery is required.
736
[ANSI-object-type ANSI-name, Partition partition-id,] [File filename]
missing on backup system
ANSI-object-type
is the ANSI object type (for example, table, index, and so on.).
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 could not obtain information about the specified ANSI table or Guardian
file. Before an updater can apply audit records to the underlying table or Guardian file, it must
obtain information about the object. The probable reason why information could not be obtained
is that the ANSI table or Guardian file has not yet been created on the backup system.
Effect The updater delays for 30 seconds and then tries to obtain the information again.
Recovery If the specified file is an Enscribe file, you must create the file on the backup system.
You should always create SQL objects on the backup system first and then create them on the
primary system.
737
RDF extractor establishing synch
Cause When the extractor is starting or restarting, it must send 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 its
starting position.
Effect The extractor attempts to become synchronized with the receiver.
Recovery This is an informational message; no recovery is required.
738
RDF extractor synch established SNO sno RBA rba
sno
is the sequence number of the TMF Master Audit Trail (MAT) for which the synchronization
point was established.
rba
is the relative byte address of the synchronization point.
Cause This message indicates that the receiver has sent the extractor a starting position in
the TMF audit trail, and that the extractor has thereby become synchronized with the receiver.
Effect Extractor is synchronized with the receiver.
Recovery This is an informational message; no recovery is required.
739
File creation failed. Error error On filename
error
is the file-system error number that identifies the specific error.
RDF Messages 375