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

Tell your database administrator that this error occurred. The database administrator should
consider checking the synchronization of the primary and backup databases.
722
Waiting for audit trail file restoration, SNO sno
sno
is the sequence number of the audit trail for which the extractor is waiting.
Cause
The extractor has requested that the specified audit trail file be restored.
Effect
The extractor waits until the audit trail file is restored.
Recovery
If you are dumping audit trails to tape and you have already mounted the correct tape, then this
is an informational message. If you have not mounted the tape, check the EMS log to see what
tape the TMF product requires and mount that tape.
723
Irrecoverable error on audit trail file filename at 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 irrecoverable error at the designated relative byte address (rba)
in the designated TMF audit trail file. This message indicates an internal RDF or TMF error.
Effect
This is a catastrophic error; the extractor abends, and RDF stops.
Recovery
Because this message indicates a system error, you should preserve the indicated audit trail file
for further analysis by your service provider.
724
RDF TAKEOVER has completed successfully
Cause
The purger has determined that all updaters have processed through to the end of the image
trail and the RDF TAKEOVER operation has completed.
Effect
Normal purger shutdown processing continues. When the purger stops, the TAKEOVER operation
will be finished.
Recovery
This is an informational message; no recovery is required.
725
RDF TAKEOVER has not completed
Cause
One of two conditions caused this event.
• UPDATE was OFF when the purger began the RDF TAKEOVER operation.
• At least one updater process terminated prematurely, without processing through to the end
of the image trail. The premature updater shutdown might have resulted from a double CPU
354 Messages