The Question is:
Dear Wizard, I restored a file from tape to disk, and the process failed after
the file had been restored. The file is complete but appears to have 0 blocks.
When I try to use it (to restore a RDB database) this happens:
$ rmu/restore/log/nocdd/noafter $diskw:[backup]data.rbf
%RMU-I-RESTXT_04, Thread 1 uses devices $DISKW:
%RMU-F-BUFFERSLOST, all buffers are lost
%RMU-F-FATALERR, fatal error on RESTORE
Is there a way I can "repair" the file to make it usable? I think the contents
of the file are ok, it just wasn4t closed properly.
Thanks in advance.
The Answer is :
If the process failed after the file had been completely restored
and correctly closed, then the file would not have had a zero block
length. Therefore, the restored Oracle Rdb backup file appears
potentially incomplete and/or otherwise corrupted.
If you wish to pursue the existing -- and potentially incomplete
or otherwise corrupted file -- then you will want to try to use
the SET FILE/END command. This command will move the end of file
(EOF) marker to the end of the file. This command will not
repair an incomplete or otherwise corrupted file.
If the SET FILE/END command fails to render the potentially
incomplete or otherwise corrupted file accessable to Oracle RMU
tool, you will also want to enlist the assistance of Oracle Rdb
support, and you will particularly want to expect to have to
convince Oracle support that you should not simply try the
As for the OpenVMS Wizard, the Wizard remains unconvinced that
salvaging a partially-restored and potentially incomplete and/or
otherwise corrupted file is advisable and wise. Rather, the
OpenVMS Wizard would encourage you to simply restore the file
from tape again.
Given that you are even asking the question, the OpenVMS Wizard
will further assume that the tape has been overwritten or otherwise
corrupted. As such, you might be able to recover some of the
data, but this will likely involve the assistance of a media
recovery service if this is a DDS (DAT) or DLT or similar tape
that has been overwritten.
Topics specific to unintential initialization or the overwriting of
disk and tape media include (1286) and (6990).
For errors resulting from file structure, directory structure, or
file structure corruptions, please see topics such as (1213), (4088),
(4571), (5071), (5553), (5719), (6021), (6234).
Disk bad block handling is discussed in topic (6926).
If you want to overwrite the data on the media, related topics
include (841), (3926), (4286), (4598), and (7320).