RECOVERY (Rebuild a Database) › Types of Recovery › RXXs without End-of-File or Trailer Records

RXXs without End-of-File or Trailer Records

If the operating system or the Multi-User Facility terminates abnormally while CA Datacom/DB is writing to a Recovery File (RXX), the tape has no End-of-File or trailer records.

When you restart the Multi-User Facility, DBUTLTY detects the condition and reports the last completed cycle number. The restart process then changes the cycle and the log blocks being spilled from a being spilled status to a needing to be spilled status. A later spill can then copy these blocks in their entirety.

Two problem situations exist at this point:

• Because no trailer records exist on the active recovery tape, recovery processing with this tape is a problem. Backward recovery cannot function at all because the trailer records cannot be found. Forward recovery can function, but the recovery receives an I/O error.
• The second problem is that when executing forward recovery, the next Recovery File after the one with no End-of-File, detects errors because of the duplicated log records which require review.

To eliminate these problems, execute the RXXFIX function RXXFIX (Recover End-Of-File).