> First time I have struck this. After recently upgrading from 1.5.5 to
> 2.1.2
> (not saying that has anything necessarily to do with it)
> I got one error as follows in a backup log:
>
> gbak: writing data for table ERSCLIENTSITES
> gbak: ERROR:BLOB not found
> gbak: ERROR: gds_$receive failed
> gbak:Exiting before completion due to errors
>
> So I ran the backup again and got no error here:
>
> gbak: writing data for table ERSCLIENTSITES
> gbak:3563 records written
> gbak: writing index PK_ERSCONTRACTYPE
>
> Does anyone know what can cause this?
> database is not being accessed at the time of backup. Subsequent test
> restore also did not present any errors.
>
>
>  regards
>  Alan McDonald
>

Bump...
this error has occurred twice now in 5 days with the intervening days not
presenting the error.
I have tracked it down this time to one blob field (value) in this table
which is a simple plain text blob, which I updated manually and this fixed
the backup error.
(I found which row was causing it by doing a select with ISQL which stops at
the exact row)
A Validation run shows no errors.
Can anyone tell me which gbak or gfix options (in which
combination/sequence) might reveal this problem and perhaps fix it (without
do this manual update, backup/restore cycle)?
thanks
Alan