RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

Cause
The purger logs this message after the successful completion of an RDF takeover operation.
• If all data volumes on the primary system are configured to the MAT, then the reported
position is the end of the last record received from the extractor.
• If any data volumes on the primary system are configured to auxiliary audit trails, then the
reported position is the end of the last commit or abort record received from the extractor
for which no data from any auxiliary audit trail is missing.
Effect
The MAT position is used for two purposes:
• 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.
358 Messages