Jason Dodson wrote:

> Corrupt binaries almost NEVER keep working past the point of corruption.

Right.

> ... I think the more likely culprit is a corrupted database...

That's not the problem with a restore. Possibly a corrupted backup file
- though the file restores OK elsewhere.


My guess, based on the spot where the restore fails is that there;s some
I/O error during the sort that precedes building an index. Restoring a
backup can use a lot of disk when sorting records to create indexes.
The two factors that affect the size of the sort temporary areas are the
number of records and the length of the keys - record length alone
doesn't enter into it. If that particular system was running out of
sort temp space at an awkward moment, that could cause an error that
gbak handles badly.


Regards,


Ann